Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

structured `void` dtypes

Open
#92 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
numpy, python
Domain
tooling

Research direction

Start by reviewing the existing typing for the void scalar and the numpy.lib.recfunctions stubs. Define how optional nested .fields mappings and possibly .shape should be represented generically, then update the related recfunctions types. Done means void supports the intended precise TypedDict-based structure and the dependent stubs remain consistent.

Written by the indexing model from the issue text.

Description

numpy.generic stubs: Enhancement topic: structured dtypes

The void scalar type should be made generic, with parameters bound to the (optional) nested field dtypes (.fields), and perhaps also its shape (.shape).

The fields type parameter should be bound to Mapping[str, tuple[dtype, int] | tuple[dtype, int, str]] | None, so that a TypedDict can be used to precisely specify the structure.

Note to self: Once implemented, be sure to also update the numpy.lib.recfunctions accordingly.

Dominant language
Python
Stars
79
Forks
8
No merged PRs in 30d

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 numpy/numtype

All issues in numpy/numtype

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.