-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
DEP: add PendingDeprecation to matlib.py funky namespace #15381
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
Conversation
We should probably stick a |
Yes, makes sense to put the same warning as for |
@mhvk I'm happy to add the warning if you'd like. |
Sounds good to me, but I'll let @eric-wieser take charge (I've somewhat dropped out of numpy stuff) |
Please add a DeprecationWarning, you can see the pattern in |
Wording taken from #10142 |
2c01658
to
0c98fb0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, please note that deprecations should be discussed on the mailing list.
0c98fb0
to
4155213
Compare
26bd5e7
to
4155213
Compare
4155213
to
581f166
Compare
@rgommers happy to merge? |
Yes, LGTM now, thanks |
Thanks @sethtroisi |
Blame, the
(FIXME: this makes little sense)
note was added by @rgommers in 2019. "from numpy import *" has existed since ~2010. Hopefully this better explains why the * import is needed.doc/source/reference/routines.matlib.rst is also available at https://docs.scipy.org/doc/numpy/reference/routines.matlib.html if that would be a better link