[Python-3000] None in Comparisons

Barry Warsaw barry at python.org
Tue Nov 11 15:07:55 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Nov 11, 2008, at 8:54 AM, M.-A. Lemburg wrote:

> On 2008-11-11 14:28, Antoine Pitrou wrote:
>> M.-A. Lemburg <mal <at> egenix.com> writes:
>>> Why was the special case for None being "smaller" than all other
>>> objects in Python removed from Python 3.0 ? (see object.c in Py2.x)
>>
>> Because ordered comparisons (<, <=, >, >=) are much stricter in 3.0  
>> than in 2.x.
>> In practice, ordered comparisons which don't have an obvious,  
>> intuitive meaning
>> now raise a TypeError (such as comparing a number and a string).
>
> That's fine. I'm just talking about the special case for None that
> has existed in Python for years - and for a good reason.

How hard is it to implement your own "missing" object which has the  
desired semantics?  Why should something as fundamental as None have it?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQCVAwUBSRmRu3EjvBPtnXfVAQKfMgQAkV5Gm6xqRlJsPZs2SEy6kisLp//V1vlT
vGeDbF2jL+N717o2cIU21PQVWONarCStR+u98SO5EUkAAqUcKZ8gJ5x+RN376djv
fg0YsqFrgtTyFaUpfOdxc648xkbL29TK+ClX0twSG5vf+5vFs4uc4SCj7bUd6+hc
xyLqUXrybwM=
=YnKH
-----END PGP SIGNATURE-----


More information about the Python-3000 mailing list