RetroSearch Browse

Tue Feb 18 22:27:15 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-February/132483.html

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.

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-February/132483.html below:

[Python-Dev] python 3 niggle: None < 1 raises TypeError