[Numpy-discussion] Issues to fix for 1.7.0rc2.
Dag Sverre Seljebotn
Wed Feb 6 03:18:39 CST 2013
On 02/06/2013 08:41 AM, Charles R Harris wrote:
> On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout
> <firstname.lastname@example.org <mailto:email@example.com>> wrote:
> On 2/6/13 12:46 AM, Charles R Harris wrote:
> > if we decide to do so
> I should mention that we don't really depend on either behavior (we
> probably should have a better doctest testing for an array of None
> values anyway), but we noticed the oddity and thought we ought to
> mention it. So it doesn't matter to us which way the decision goes.
> More Python craziness
> In : print None or 0
> In : print 0 or None
To me this seems natural and is just how Python works? I think the rule
for "or" is simply "evaluate __nonzero__ of left operand, if it is
False, return right operand".
The reason is so that you can use it like this:
x = get_foo() or get_bar() # if get_foo() returns None
# use result of get_bar
x = x or create_default_x()
I guess that after the "a if expr else b" was introduced this has become
> Numpy any is consistent with python when considered as logical_or.reduce
> In : print array([0, None]).any()
> In : print array([None, 0]).any()
> This appears to be an __ror__, __or__ inconsistency in python. Note that
> None possesses neither of those operators.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion