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 josh.r
Recipients Nicholas Matthews, docs@python, josh.r, matrixise
Date 2019-05-17.15:27:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558106844.51.0.682110067093.issue36947@roundup.psfhosted.org>
In-reply-to
Content
Clarification is fine, but "MyClass and MySubclass are instances of Meta:" is 100% true. Declaring a class to have a metaclass (or inheriting from a class with a metaclass) means that the class itself is an instance of the metaclass.

New instances of the classes with metaclass Meta are not "created using Meta"; Meta modifies the creation of the classes themselves, not instances of the classes.

Point is, your suggested change is half wrong (new instances of MyClass and MySubclass aren't directly created using Meta), and half misunderstanding the current documentation ("MyClass is an instance of Meta" already means "MyClass has the metaclass Meta").
History
Date User Action Args
2019-05-17 15:27:24josh.rsetrecipients: + josh.r, docs@python, matrixise, Nicholas Matthews
2019-05-17 15:27:24josh.rsetmessageid: <1558106844.51.0.682110067093.issue36947@roundup.psfhosted.org>
2019-05-17 15:27:24josh.rlinkissue36947 messages
2019-05-17 15:27:24josh.rcreate