Skip to content
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

DOC: change all non-code instances of Numpy to NumPy #8021

Merged
merged 6 commits into from
Sep 7, 2016

Conversation

pdebuyl
Copy link
Contributor

@pdebuyl pdebuyl commented Sep 5, 2016

Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.

see issue #7986

@btel
Copy link
Contributor

btel commented Sep 6, 2016

It looks good. However, I would not change the release notes - it might look strange that the last commit is after the release date.

Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.

Release notes were left unchanged.

see issue numpy#7986
@pdebuyl
Copy link
Contributor Author

pdebuyl commented Sep 6, 2016

Forced pushed the PR with no changes to release notes.

@btel
Copy link
Contributor

btel commented Sep 6, 2016

I also opened an associated PR for the website: numpy/numpy.org#5

@pdebuyl
Copy link
Contributor Author

pdebuyl commented Sep 6, 2016

Should I also do the code part? The docstrings are full of both both versions, including C files in multiarray, umath and mtrand.

@btel
Copy link
Contributor

btel commented Sep 6, 2016

I think the docstrings and comment could be updated, but not the source code.

The strings in error messages were left untouched
the files in doc/ and numpy/ were covered in previous commits
@charris charris changed the title change all non-code instances of Numpy to NumPy DOC: change all non-code instances of Numpy to NumPy Sep 6, 2016
@btel
Copy link
Contributor

btel commented Sep 6, 2016

It looks good to me.

@@ -1,4 +1,4 @@
Numpy.i: a SWIG Interface File for NumPy
NumPy.i: a SWIG Interface File for NumPy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be changed to all lower case, numpy.i, which is the actual name of the file it refers to.

@jaimefrio
Copy link
Member

Thanks a lot for doing this!

That was a lot of NumPy to read, but I found one instance that needs to be corrected, see inline comment. My diagonal looking at the rest didn't find anything else. Should I merge it once you change the SWIG file name, or is there anything else you want to include in this PR?

@pdebuyl
Copy link
Contributor Author

pdebuyl commented Sep 6, 2016

You are welcome :-) It is my pleasure to contribute to NumPy in the extent of my abilities and time!

The PR is complete as it is. There is also a need for a statement about the capitalization somewhere (see #7986) but that is for later.

@btel
Copy link
Contributor

btel commented Sep 6, 2016

@pdebuyl @jaimefrio could you also take a look at numpy/numpy.org#5?

Should these changes be mentioned in the release notes for the next release?

@@ -2,4 +2,4 @@
Numarray compatibility
**********************

The numarray module was removed in Numpy 1.9.
The numarray module was removed in NumPy 1.9.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should make the 1.9. 1.9.0. as below.

@@ -742,7 +742,7 @@ def fit(cls, x, y, deg, domain=None, rcond=None, full=False, w=None,
deg : int or 1-D array_like
Degree(s) of the fitting polynomials. If `deg` is a single integer
all terms up to and including the `deg`'th term are included in the
fit. For Numpy versions >= 1.11 a list of integers specifying the
fit. For NumPy versions >= 1.11 a list of integers specifying the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.11.0

@charris
Copy link
Member

charris commented Sep 6, 2016

I made comments about changing version references from the form 1.10. to 1.10.0. Strictly speaking, that is unrelated to the NumPy changes, but I think it best to settle on using a full version string.

@pdebuyl
Copy link
Contributor Author

pdebuyl commented Sep 7, 2016

Hi,
I made the changes and spotted a few more instances close to existing capitalization changes, that I also updated.

@jaimefrio jaimefrio merged commit b91e8d8 into numpy:master Sep 7, 2016
@jaimefrio
Copy link
Member

Thanks Pierre!

@pdebuyl
Copy link
Contributor Author

pdebuyl commented Sep 7, 2016

Thanks @btel @charris @jaimefrio for guidance :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants