Message182846
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 should best get what they wanted with a range subclass, if that were made possible, Nick C. replied "I wasn't even aware you *couldn't* subclass it (I'd never tried).". Indeed, why would he with no doc.
The types module doc could also use an addition.
Attached subclassable.py produces these lists:
Among named builtin classes, these cannot be subclassed:
bool, memoryview, range, slice,
Among types classes, these can be subclassed:
ModuleType, SimpleNamespace, |
|
Date |
User |
Action |
Args |
2013-02-24 01:53:01 | terry.reedy | set | recipients:
+ terry.reedy, daniel.urban, docs@python |
2013-02-24 01:53:01 | terry.reedy | set | messageid: <1361670781.33.0.576202819259.issue17279@psf.upfronthosting.co.za> |
2013-02-24 01:53:01 | terry.reedy | link | issue17279 messages |
2013-02-24 01:53:01 | terry.reedy | create | |
|