8000 1.10 deprecated removal by charris · Pull Request #5990 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

1.10 deprecated removal #5990

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

Merged
merged 9 commits into from
Jun 21, 2015
Merged

Conversation

charris
Copy link
Member
@charris charris commented Jun 20, 2015

Remove some deprecated bits and mark all Deprecations with a date and Numpy version for further action.
This PR is not finished yet, but need review anyway ;)

One question is what to do with deprecated C-API functions, of which there are four. We can't remove them, but perhaps we should return an error. Thoughts?

@charris charris added this to the 1.10.0 release milestone Jun 20, 2015
@charris
Copy link
Member Author
charris commented Jun 20, 2015

The first commit may break older versions of SciPy, although Scipy currently does not use the Numpy version anywhere.

@charris charris force-pushed the 1.10-deprecated-removal branch 3 times, most recently from 0301562 to 6318c68 Compare June 20, 2015 20:12
@charris
Copy link
Member Author
charris commented Jun 20, 2015

That's all folks.

@@ -384,6 +384,7 @@ PyUFunc_NegativeTypeResolver(PyUFuncObject *ufunc,

/* The type resolver would have upcast already */
if (out_dtypes[0]->type_num == NPY_BOOL) {
/* 2013-12-05, 1.9 */
if (DEPRECATE("numpy boolean negative (the unary `-` operator) is "
Copy link
Member

Choose a reason for hiding this comment

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

Not your job, but just noticed that there is a copy paste error here, The message should ask to use ~ I think.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed, will fix.

@charris charris force-pushed the 1.10-deprecated-removal branch from 16c3502 to 20860e6 Compare June 21, 2015 18:42
charris added 3 commits June 21, 2015 12:43
These functions npy_PyFile_Dup and npy_PyFile_DupClose do not work
correctly in Python 3. Deprecation messages have been raised in
npy_PyFile_Dup since 1.9 and it is probably best to smoke out any
remaining uses by simply removing the function.
This was deprecated in NumPy 1.7 with a warning that it would raise
an error in the future. Tests for the new error are added and the
test that allowed that special case is removed.
This is to make it easier to find and remove deprecated features.
It would be a good idea if all deprecations were made with similar
comments.
@charris charris force-pushed the 1.10-deprecated-removal branch from 20860e6 to 2205136 Compare June 21, 2015 18:43
@charris
Copy link
Member Author
charris commented Jun 21, 2015

OK, fixed the quibbles and removed the last two risky deprecation removals for a separate PR.

charris added 6 commits June 21, 2015 13:46
Was in numpy/distutils/exec_command.py.
Update 1.10-notes.rst.
Deprecated functions in numpy/distutils/command/config.py.
Deprecated, removed from numpy/core/arrayprint.py.
Some keywords are deprecated and slated for removal in numpy 2.0.
Add comment to deprecation date to clarify that.
@charris charris force-pushed the 1.10-deprecated-removal branch from 2205136 to a27f560 Compare June 21, 2015 19:46
charris added a commit that referenced this pull request Jun 21, 2015
@charris charris merged commit e3b2bc0 into numpy:master Jun 21, 2015
@charris charris deleted the 1.10-deprecated-removal branch June 21, 2015 22:18
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.

2 participants
0