Improve dask typing

Open
#41 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
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

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.

Description

component: documentation type: dask

This tracks untyped Dask APIs that we use.

  • dask.visualize is 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, …
Dominant language
Python
Stars
15
Forks
5
Avg merge
10h 33m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

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/fast-array-utils

All issues in scverse/fast-array-utils

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.