move the `numpy._typing._char_codes` literals to `_numtype`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing issue #566 and the current definitions in numpy._typing._char_codes and _numtype. Confirm that the _DTypeLike* aliases have been removed, then identify the literals to relocate and establish the intended naming scheme. Done means the literals live in _numtype under the improved names without leaving the old definitions behind.
Written by the indexing model from the issue text.
Description
This has to wait until after the _DTypeLike* aliases are removed (#566).
It's also a good idea to use a better naming scheme, while we're at it.
- Dominant language
- Python
- Stars
- 79
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from numpy/numtype
-
topic: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
topic: documentation
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
blame: Pyright tool: basedpyright
-
numpy.generic stubs: Incomplete
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
_numtype stubs: Refactor
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100