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 ncoghlan
Recipients abacabadabacaba, arigo, docs@python, eric.snow, levkivskyi, ncoghlan, r.david.murray, rhettinger
Date 2015-08-05.14:51:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438786311.16.0.572674033564.issue24129@psf.upfronthosting.co.za>
In-reply-to
Content
I merged Ivan's latest patch to 3.4/3.5/default. We're unlikely to ever be able to make these docs completely intuitive (as name resolution is genuinely complex), but Ivan's revisions at least mean we're no longer assuming readers know how the name resolution worked prior to the introduction of lexical scoping, and a couple of tricky cases now have inline examples.

I also noticed an existing paragraph in the docs that *I* didn't understand, and filed issue #24796 to cover that. I'm not sure if we should just delete the paragraph, or if we accidentally dropped a compile time error check that didn't have any tests to ensure we were detecting the problem.
History
Date User Action Args
2015-08-05 14:53:17ncoghlanunlinkissue24129 messages
2015-08-05 14:51:51ncoghlansetrecipients: + ncoghlan, arigo, rhettinger, r.david.murray, abacabadabacaba, docs@python, eric.snow, levkivskyi
2015-08-05 14:51:51ncoghlansetmessageid: <1438786311.16.0.572674033564.issue24129@psf.upfronthosting.co.za>
2015-08-05 14:51:51ncoghlanlinkissue24129 messages
2015-08-05 14:51:49ncoghlancreate