Contributing to NumPy — NumPy v2.6.dev0 Manual

numpy.org

Learn | NEPs | User Guide | API reference | Building from source | Release notes | AI Policy | Spin: NumPy’s developer tool | Development workflow | Reviewer guidelines | NumPy benchmarks | NumPy C style guide | For downstream package authors | Releasing a version | NumPy governance | Building the NumPy API and reference docs | How to contribute to the NumPy documentation | Advanced debugging tools | Setting up and using your development environmen | Using GitHub Codespaces for NumPy development

Tin mới

Understanding NumPy’s versioning and API/ABI stability

Not a coder? Not a problem! NumPy is multi-faceted, and we can use a lot of help. These are all activities we’d like to get help with (they’re all important, so we list them in alphabetical order):

properly formatted

Commit locally as you progress (git add and git commit) Use a properly formatted commit message, write tests that fail before your change and pass afterward, run all the tests locally. Be sure to document any changed beh

properly formatted

Commit locally as you progress (git add and git commit) Use a properly formatted commit message, write tests that fail before your change and pass afterward, run all the tests locally. Be sure to document any changed beh

Reviewer Guidelines

NEP 23 deprecation policy

(in NumPy Enhancement Proposals)

Spin: NumPy’s developer tool

Building the NumPy API and reference docs

Finding C errors with additional tooling

Using GitHub Codespaces for NumPy development

Benchmarking versions

How to prepare a release

NumPy project governance and decision-making

How to contribute to the NumPy documentation

1 1