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 lpd
Recipients amaury.forgeotdarc, georg.brandl, lpd
Date 2008-01-05.19:35:30
SpamBayes Score 0.0533252
Marked as misclassified No
Message-id <1199561731.42.0.735388236358.issue1734@psf.upfronthosting.co.za>
In-reply-to
Content
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 calling a class object is a
new instance of that class, but it doesn't mention __new__. So perhaps
it would OK to just add something like the following to 3.4.3:

Note that if a metaclass is a subclass of <code>type</code>, it should
override <code>__new__</code>, not <code>__call__</code>.
History
Date User Action Args
2008-01-05 19:35:31lpdsetspambayes_score: 0.0533252 -> 0.0533252
recipients: + lpd, georg.brandl, amaury.forgeotdarc
2008-01-05 19:35:31lpdsetspambayes_score: 0.0533252 -> 0.0533252
messageid: <1199561731.42.0.735388236358.issue1734@psf.upfronthosting.co.za>
2008-01-05 19:35:30lpdlinkissue1734 messages
2008-01-05 19:35:30lpdcreate