[Python-Dev] python 3 niggle: None < 1 raises TypeError
Glenn Linderman
v+python at g.nevcal.com
Tue Feb 18 23:34:41 CET 2014
More information about the Python-Dev mailing list
Tue Feb 18 23:34:41 CET 2014
- Previous message: [Python-Dev] python 3 niggle: None < 1 raises TypeError
- Next message: [Python-Dev] python 3 niggle: None < 1 raises TypeError
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2/18/2014 1:27 PM, Greg Ewing wrote: > M.-A. Lemburg wrote: >> The alternative would be adding a new singleton to mean mostly >> the same thing as None, but having the property of comparing >> less than all other objects and then recommend its use in the >> DB-API for Python 3 applications... > > Which I think would be a *really bad* idea, because > there would then no longer be One Obvious Way to > represent and process null values. > > E.g. you would no longer be able to write > 'value is None' and trust it to work on all kinds > of null value you're likely to get. Of course you couldn't... value is None would never work full Null values, only for None, like it should. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140218/0a0fb4fb/attachment.html>
- Previous message: [Python-Dev] python 3 niggle: None < 1 raises TypeError
- Next message: [Python-Dev] python 3 niggle: None < 1 raises TypeError
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list