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 eric.araujo
Recipients Piotr.Kuchta, ashwch, docs@python, eric.araujo, ezio.melotti, jeffknupp
Date 2013-03-08.16:29:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362760160.44.0.425280325386.issue17383@psf.upfronthosting.co.za>
In-reply-to
Content
> It is customary *but not required* to place all import statements at the
> beginning of a module...". The third seems to state that regardless of
> whether or not you followed the custom, module names are always placed in
> the global symbol table

Yes. Not following the usage means placing imports in the middle of the module for example, but it does not imply imports in functions.
History
Date User Action Args
2013-03-08 16:29:20eric.araujosetrecipients: + eric.araujo, ezio.melotti, docs@python, jeffknupp, ashwch, Piotr.Kuchta
2013-03-08 16:29:20eric.araujosetmessageid: <1362760160.44.0.425280325386.issue17383@psf.upfronthosting.co.za>
2013-03-08 16:29:20eric.araujolinkissue17383 messages
2013-03-08 16:29:20eric.araujocreate