[Numpy-discussion] Issues to fix for 1.7.0rc2.
Jason Grout
jason-sage at creativetrax.com
Wed Feb 6 00:23:19 EST 2013
On 2/4/13 12:04 AM, Ondřej Čertík wrote:
> Hi,
>
> Here are the last open issues for 1.7, there are 9 of them:
>
> https://github.com/numpy/numpy/issues?milestone=3&sort=updated&state=open
>
Here's something we noticed while working on getting 1.7rc1 into Sage
with one of our doctests. With numpy 1.5.1 (we skipped 1.6.x because of
backwards compatibility issues...):
import numpy as np
print np.array([None, None]).any()
prints False, but with 1.7.rc1, we get None.
For comparison, in Python 2.6.1 and 3.3.0:
>>> any([None,None])
False
>>> print None or None
None
Was this change between 1.5.1 and 1.7 intentional?
Thanks,
Jason
More information about the NumPy-Discussion
mailing list