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 jeffknupp
Recipients Piotr.Kuchta, ashwch, docs@python, eric.araujo, ezio.melotti, jeffknupp
Date 2013-03-08.16:45:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362761151.06.0.756040186108.issue17383@psf.upfronthosting.co.za>
In-reply-to
Content
Of the "two different things", the first (the scope of imported names) is never covered in the documentation. As a result, the text in question seems to imply an import statement can *only* be in module scope. 

From the reader's perspective: "If I wanted to import something in a class or function it obviously can't be at the top of the file, so I guess I can't do that." The tutorial doesn't disabuse them of this notion.
History
Date User Action Args
2013-03-08 16:45:51jeffknuppsetrecipients: + jeffknupp, ezio.melotti, eric.araujo, docs@python, ashwch, Piotr.Kuchta
2013-03-08 16:45:51jeffknuppsetmessageid: <1362761151.06.0.756040186108.issue17383@psf.upfronthosting.co.za>
2013-03-08 16:45:51jeffknupplinkissue17383 messages
2013-03-08 16:45:50jeffknuppcreate