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 r.david.murray
Recipients guettli, r.david.murray
Date 2017-07-17.15:17:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500304677.99.0.723102469675.issue30948@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the suggestion, but I don't think so.

Python imports are not lazy.  They are ordered.  Python is an *interpreted* language, so __subclasses__ is only going to hold those subclasses whose class definitions have been executed. This is fundamental to how the language works, and does not warrant a special note here.  Note that the entry already includes something that should give a strong hint about this even if you hadn't previously thought about it: the statement that it only includes subclasses that are "still alive".  This implies they aren't in the list until they become alive.
History
Date User Action Args
2017-07-17 15:17:58r.david.murraysetrecipients: + r.david.murray, guettli
2017-07-17 15:17:57r.david.murraysetmessageid: <1500304677.99.0.723102469675.issue30948@psf.upfronthosting.co.za>
2017-07-17 15:17:57r.david.murraylinkissue30948 messages
2017-07-17 15:17:57r.david.murraycreate