consider removing `_copy` private method

Open
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start by reading src/spatialdata_plot/pl/basic.py around line 81 and tracing where the private _copy method is used. Investigate whether plotting can avoid copying the entire spatialdata object when elements are in memory. Done means preserving existing plotting behavior while avoiding the expensive full-object copy; no test file is named in the issue.

Written by the indexing model from the issue text.

Description

enhancement priority: low
Report

https://github.com/scverse/spatialdata-plot/blob/582c8379f2478d0e7bc0a7d4733d3cb6fa9af061/src/spatialdata_plot/pl/basic.py#L81

copying the entire spatialdata object can be expensive if elements are on memory. Consider change logic to avoid this.

Version information

No response

Dominant language
Python
Stars
86
Forks
21
Avg merge
14h 50m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scverse/spatialdata-plot

All issues in scverse/spatialdata-plot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.