scverse / scverse/fast-array-utils
Improve dask typing
Open
Nobody has claimed this yet.
component: documentation
type: dask
- Dominant language
- Python
- Stars
- 15
- Forks
- 5
- Avg merge
- 10h 33m
- Merged PRs (30d)
- 9
Description
This tracks untyped Dask APIs that we use.
-
dask.visualizeis not exported
The following APIs we use in the dask repo are untyped:
-
da.Array.visualize/dask.visualize -
da.Array.compute/dask.compute -
da.Array.map_blocks/da.map_blocks -
da.Array.map_overlap/da.map_overlap -
da.reduction -
da.from_array - Creation methods like
da.zeros, …
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the typing and export entry points for the listed Dask APIs, beginning with dask.visualize. Review the APIs named in the checklist—visualize, compute, map_blocks, map_overlap, reduction, from_array, and creation methods—and determine the project’s existing typing conventions. Done means the tracked APIs are typed and dask.visualize is exported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100