- Development
- Release management
- Reference
- Tools
- Plans
- Hacking Notes
This is the Trac page for NumPy. SciPy development takes place here.
This is the "hard-hat" area for NumPy development. Here we track issues, document design decisions, outline areas of NumPy that needs work, etc.
Quick Start
In order to create or edit wiki pages and tickets, you need to register first.
- File a bug report or feature request
- Write documentation
Development
- NumPy GitHub repository
- NumPy development guide
- Review pull requests
- Testing guidelines
- DevelopmentTips
Release management
- Making releases
- ApiDeprecation
Reference
- NumPy reference
- NumPy C-API reference
- C coding style guidelines
- Documentation style guidelines
- numpy.distutils doc
Tools
- EmacsSetup
- `reindent` and other scripts from the Python repository
Plans
- DocDays
- ProjectIdeas
- G3F2PY
- BufferPEP
- ZeroRankArray
- ZeroStrideArray
- MaskedArray
- MaskedArrayAlternative
- MaskedArrayApiChanges
- TransitionStories
- PossibleOptimizationAreas
- NumScons
- DistutilsRevamp
- ProperNanHandling
- MicrosoftToolchainSupport (python 2.6, 64 bits, Visual studio 2005/2008)
- ImprovingIssueWorkflow
- NumPyRefactoring
- NdarrayWithNamedAxes
Hacking Notes
Various comments about the internal structure of the numpy code.
- DtypeKinds
- GitMigrationProposal
- Developing NumPy with git
- Git: rebase or merge? article.gmane.org/gmane.comp.video.dri.devel/34744