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 georg.brandl, onlyme, r.david.murray
Date 2009-08-24.14:55:41
SpamBayes Score 1.103484e-11
Marked as misclassified No
Message-id <1251125743.41.0.272422739212.issue6761@psf.upfronthosting.co.za>
In-reply-to
Content
FYI, all special methods are (now) looked up on the type for new style
classes.  Your suggested rewrite makes things more confusing, IMO
(partly because to make it accurate it would need to be something like
type(x).__call__(x, *args, **kw), which doesn't really make the sentence
clearer).

So far I haven't thought of a rewording I like.  The best I've come up
with is "x(arguments) invokes the __call__ method, passing it the
arguments."  This leaves it to other parts of the language spec to
explain how __call__ gets resolved.

Whatever we decide to do, section 3.4.4 will need a similar update.
History
Date User Action Args
2009-08-24 14:55:43r.david.murraysetrecipients: + r.david.murray, georg.brandl, onlyme
2009-08-24 14:55:43r.david.murraysetmessageid: <1251125743.41.0.272422739212.issue6761@psf.upfronthosting.co.za>
2009-08-24 14:55:42r.david.murraylinkissue6761 messages
2009-08-24 14:55:41r.david.murraycreate