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 docs@python, levkivskyi, r.david.murray, rhettinger
Date 2015-06-19.19:46:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1434743220.26.0.736367463071.issue24129@psf.upfronthosting.co.za>
In-reply-to
Content
In this particular case, just wait (now that you have pinged the issue).  Raymond is the most likely person to figure out how to phrase this better, but it isn't obvious what the best way to explain this is.  I don't think your explanation is exactly correct, but I don't know enough about how class name resolution is implemented to explain what's wrong with it, I just know it doesn't feel quite right :)  (Of course, I might be wrong.)

Ping the issue again in a few weeks if there is no action.
History
Date User Action Args
2015-06-19 19:47:00r.david.murraysetrecipients: + r.david.murray, rhettinger, docs@python, levkivskyi
2015-06-19 19:47:00r.david.murraysetmessageid: <1434743220.26.0.736367463071.issue24129@psf.upfronthosting.co.za>
2015-06-19 19:47:00r.david.murraylinkissue24129 messages
2015-06-19 19:46:59r.david.murraycreate