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

pylab's all() and Python's built in all() give different res #194

Closed
ddale opened this Issue Jun 20, 2011 · 1 comment

Comments

Projects
None yet
2 participants
@ddale
Contributor

ddale commented Jun 20, 2011

Original report at SourceForge, opened Thu Feb 17 04:27:59 2011

pylab's all() and Python's built in all() give different results.
This is detailed here: http://bugs.python.org/issue11221

This looks like a bug, but it actually may be legitimate functionality. If this is the case, this ticket might be better served as a feature request to change the name of pylab's all to something else to allow use of "from pylab import*" without harm to existing code.

@efiring

This comment has been minimized.

Member

efiring commented Jun 21, 2011

Pylab simply dumps everything from pyplot and numpy into its namespace, and
all() comes from numpy. That is the way it has been for a long time, so I
don't think we are going to change anything unless numpy does so. A name
change such as you suggest could harm existing code that is assuming the
present behavior. In the meantime, this illustrates why we discourage use
of "from pylab import *", especially for new code.

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