[issue1734] documentation on metaclasses is incomplete and misleading

Georg Brandl added the comment: This should now be appropriately explained in the trunk, r59837. I also added an example of using __new__ in a metaclass. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1734] documentation on metaclasses is incomplete and misleading

L. Peter Deutsch added the comment: Actually, "called" and "callable" are OK, if the documentation says somewhere that the normal effect of "calling" a type object is to invoke __new__. The places I looked first (sections 3.1, 3.3, and 3.4.1) do not say this. 5.3.4 does say that the result of cal

[issue1734] documentation on metaclasses is incomplete and misleading

Changes by Georg Brandl: -- assignee: -> georg.brandl __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue1734] documentation on metaclasses is incomplete and misleading

Georg Brandl added the comment: I'll look into it. -- nosy: +georg.brandl resolution: invalid -> status: closed -> open __ Tracker <[EMAIL PROTECTED]> __ _

[issue1734] documentation on metaclasses is incomplete and misleading

L. Peter Deutsch added the comment: Please reopen this issue as a documentation bug. The documentation for __new__ in section 3.4.1 says: __new__() is intended mainly to allow subclasses of immutable types (like int, str, or tuple) to customize instance creation. The documentation for metaclas