None inconsistent

mjhand at mjhand at
Thu Jun 10 21:52:20 CEST 1999

Pardon the repetition (if this is repetitive).  I have posted
this message three times but have yet to see it appear on the

In 1.5.1, "None" was "less" than all numbers:
>>> 0 < None
>>> sys.maxint > None

In 1.5.2, "None" became "greater" than all numbers:
>>> 0 < None
>>> sys.maxint > None

I have three questions about this:
(1) Was this change made intentionally?  (I hope so.)
(2) Can we count on it staying this way forever?  (I hope so.)
(3) When will the starship be updated to use 1.5.2 by default?
    (/usr/bin/python == 1.5.1, /usr/local/bin/python == 1.5.2b2)

I absolutely LOVE that "None" is accepted as a valid argument in
min(), max(), and cmp(), but I would like it to behave consistently.
The 1.5.2 way is best for my code.  Please tell me it will stay
that way forever.


Sent via
Share what you know. Learn what you don't.

More information about the Python-list mailing list