Terry J. Reedy added the comment:
From the current python-ideas 'range' thread:
Me: Would it be correct to say (now) that all 4 are intentional omissions? and
not merely oversights?
Nick: Yes, I think so. People will have to be *real* convincing to explain a
case where composition isn't a more
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17279
___
___
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17279
___
___
Python-bugs-list
Terry J. Reedy added the comment:
Such a list might differentiate between classes that are intentionally not
subclassed and those for which subclassing simply has not yet been enabled.
That might help eliminate the latter list.
When I suggested on the python-ideas 'range' thread that people
Terry J. Reedy added the comment:
The list given is for 3.3. 3.2 and 2.7 do not have SimpleNamespace. I do not
have and currently cannot build 3.4 to test, but as of this moment, I expect it
to be the same. In 2.7, range is xrange. Its types module includes aliases for
builtins, such as
New submission from Terry J. Reedy:
More than once, people have noted on python-list that not all built-in classes
can be subclassed and that there seems to be no way to find out which, other
than to try each. (Today, Daniel Urban pointed out the CPython-specific
'xx.__flags__ (1 10)'.) If
Changes by Daniel Urban urban.dani...@gmail.com:
--
nosy: +daniel.urban
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17279
___
___
