A RetroSearch Logo

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

Search Query:

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

[Python-Dev] bool does not want to be subclassed?

[Python-Dev] bool does not want to be subclassed? [Python-Dev] bool does not want to be subclassed?Guido van Rossum guido at python.org
Mon Feb 16 01:00:49 EST 2004
> > there are only two different objects representing these values.
> 
> Why is this property so important?
> 
> I can understand why it's useful for there to be only
> one None, since programs do 'x is None' a lot. But it's
> not as if you can get away with saying 'x is True' or
> 'x is False' all over the place.

Why is it important *not* to have this property?  Maintaining it is
trivial, and it helps the implementation a bit (it's actually
*natural* to have only the two instances).

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4