-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unify spelling of Numpy/NumPy #7986
Comments
The choice always leaves me thinking a bit. I try to use NumPy for official stuff, but tend to fall back on numpy for informal communication. This might be a good topic to raise on the mailing list. |
The mailing-list thread has support for NumPy (uppercase N and P) from
The book by @teoliphant (still available here, for instance http://csc.ucdavis.edu/~chaos/courses/nlp/Software/NumPyBook.pdf) is "Guide to NumPy" and the intro is consistently using "NumPy". There are inconsistencies in the documentation on scipy.org but I (humbly) suggest to pick "NumPy" for the name of the project and also for reference to the software and "numpy" as the module name. The "Guide to NumPy" refers to the There is no FAQ in the documentation of NumPy but it would be good to add this information somewhere (either in the NumPy reference or in the user guide). "NumPy arrays" and "numpy arrays" can both be used, as they can refer to the project or to the module. |
@pdebuyl thanks! I updated the issue with your proposed solution. If there is no other volunteers, I can open a PR with these changes. |
I can help for this. There are 61 files in
Should the release notes be modified? They could be considered "historical" data. There are a few instances of "Numpy*" in the test code (the The C code seems to use "NumPy" consistently. |
Instances remain for NumpyVersion and Numpy.rec.fromarrays that are references to code. Release notes were left unchanged. see issue numpy#7986
@pdebuyl: Can this be closed, or is there more to do here? |
No problem for closing. The corresponding PR was merged. |
The documentation is not consistent in spelling of "NumPy" (vs "Numpy"). For example, the reference manual uses both spelling in the introduction paragraph:
What is the official spelling? Make it consistent across all documentation.
This issue was initially reported at Scipy Lectures (scipy-lectures/scientific-python-lectures#250) by @btel and @emmanuelle.
Following the discussion on the mailing list and recommendations of @pdebuyl to close the issue:
numpy
only in relation to the module nameThe text was updated successfully, but these errors were encountered: