This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients docs@python, terry.reedy
Date 2013-02-22.22:09:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361570964.09.0.896873756654.issue17279@psf.upfronthosting.co.za>
In-reply-to
Content
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 the specifics are a Python feature, rather than CPython specific, I think they should be given in the doc.

There is a recent issue, which I cannot find, about re-organizing the Library built-in functions chapter by groups. If this is done, it would be easy to add, in the introduction to built-in classes, a list of which of the named classes can or cannot be subclassed (whichever list is shorter) and note that those not in builtins cannot be.)
History
Date User Action Args
2013-02-22 22:09:24terry.reedysetrecipients: + terry.reedy, docs@python
2013-02-22 22:09:24terry.reedysetmessageid: <1361570964.09.0.896873756654.issue17279@psf.upfronthosting.co.za>
2013-02-22 22:09:24terry.reedylinkissue17279 messages
2013-02-22 22:09:23terry.reedycreate