You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Matti Picus 0f7eaf8971
Merge pull request #21922 from davidgilbertson/patch-2
2 days ago
.circleci CI: CircleCI: Install numpy after processing doc_requirements.txt 8 months ago
.github change the label to without_optimizations 3 weeks ago
benchmarks Merge pull request #12065 from MilesCranmer/master 2 weeks ago
branding/logo Set logo colors explicitly to RGB 1 year ago
doc Merge pull request #21922 from davidgilbertson/patch-2 2 days ago
numpy BUG: cross product: add dtype conversions of inputs (#20659) 2 days ago
tools CI: tools: Remove a long but obsolete comment from travis-test.sh 1 week ago
.clang-format MAINT: Standardize guards in numpy/core/src/multiarray. 10 months ago
.codecov.yml CI: Use informational mode for codecov 1 year ago
.coveragerc MAINT, TST: remove test-installed-numpy.py 3 years ago
.ctags.d DEV: add ctags option file 4 years ago
.gitattributes Merge pull request #19478 from r-devulap/svml 9 months ago
.gitignore MAINT: Update the documentation Makefile 2 weeks ago
.gitmodules MAINT: Adding SVML submodule 11 months ago
.gitpod.yml DEV: remove esbonio from gitpod initialization. (#21348) 3 months ago
.hadolint.yaml DEV: general Gitpod enhancements (#18822) 1 year ago
.lgtm.yml MAINT: mark _version.py as third-party code for LGTM 10 months ago
.mailmap MAINT: Update main after 1.23.0 release. 2 weeks ago
.travis.yml CI: Guard compile-time CPU features tests 3 weeks ago
CITATION.bib DOC: add citation file for GitHub support. 11 months ago
INSTALL.rst Rename INSTALL.rst.txt to INSTALL.rst 1 month ago
LICENSE.txt Update Copyright to 2022 6 months ago
LICENSES_bundled.txt MAINT: Linting fixes 2 years ago
MANIFEST.in Include .coveragerc to support runtests.py. #19617 11 months ago
README.md Remove the reference to the “good first issue” label 3 months ago
THANKS.txt ENH: core: Start einsum function, add copyright notices to files 12 years ago
azure-pipelines.yml Require sphinx 4.3+ 2 weeks ago
azure-steps-windows.yml Merge pull request #21558 from bsipocz/python36_37_cleanup 1 month ago
doc_requirements.txt Require sphinx 4.3+ 2 weeks ago
environment.yml Require sphinx 4.3+ 2 weeks ago
linter_requirements.txt MAINT: Bump pycodestyle from 2.7.0 to 2.8.0 9 months ago
pavement.py REL: Prepare main for NumPy 1.24.0 development 1 month ago
pyproject.toml MAINT: Update to Cython 0.29.30. 2 months ago
pytest.ini DEV: add warnings filter to pytest conf. 5 months ago
release_requirements.txt MAINT: Update towncrier version in install and notes 1 year ago
runtests.py BUG: refguide-check: respect the verbosity 2 months ago
setup.cfg DOC: Fix typos in NEPs, found by codespell 10 months ago
setup.py MAINT: Update to Cython 0.29.30. 2 months ago
site.cfg.example DOC: update docs in site.cfg.example 5 months ago
test_requirements.txt TST: Reintroduce `typing_extensions` as a test requirement 1 month ago
tox.ini MAINT: Python <3.8 related cleanups 1 month ago
versioneer.py Update versioneer.py 1 year ago

README.md


Powered by NumFOCUS PyPI Downloads Conda Downloads Stack Overflow Nature Paper

NumPy is the fundamental package for scientific computing with Python.

It provides:

  • a powerful N-dimensional array object
  • sophisticated (broadcasting) functions
  • tools for integrating C/C++ and Fortran code
  • useful linear algebra, Fourier transform, and random number capabilities

Testing:

NumPy requires pytest and hypothesis. Tests can then be run after installation with:

python -c 'import numpy; numpy.test()'

Code of Conduct

NumPy is a community-driven open source project developed by a diverse group of contributors. The NumPy leadership has made a strong commitment to creating an open, inclusive, and positive community. Please read the NumPy Code of Conduct for guidance on how to interact with others in a way that makes our community thrive.

Call for Contributions

The NumPy project welcomes your expertise and enthusiasm!

Small improvements or fixes are always appreciated. If you are considering larger contributions to the source code, please contact us through the mailing list first.

Writing code isn’t the only way to contribute to NumPy. You can also:

  • review pull requests
  • help us stay on top of new and old issues
  • develop tutorials, presentations, and other educational materials
  • maintain and improve our website
  • develop graphic design for our brand assets and promotional materials
  • translate website content
  • help with outreach and onboard new contributors
  • write grant proposals and help with other fundraising efforts

For more information about the ways you can contribute to NumPy, visit our website. If you’re unsure where to start or how your skills fit in, reach out! You can ask on the mailing list or here, on GitHub, by opening a new issue or leaving a comment on a relevant issue that is already open.

Our preferred channels of communication are all public, but if you’d like to speak to us in private first, contact our community coordinators at numpy-team@googlegroups.com or on Slack (write numpy-team@googlegroups.com for an invitation).

We also have a biweekly community call, details of which are announced on the mailing list. You are very welcome to join.

If you are new to contributing to open source, this guide helps explain why, what, and how to successfully get involved.