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:02:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362758549.43.0.924067107884.issue17383@psf.upfronthosting.co.za>
In-reply-to
Content
I think Piotr's point is the wording of the last sentence is ambiguous. The second statement reads "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.

I think the last two sentences need to be rewritten to remove ambiguity. If, at this point, we only want to explain that importing a module makes that modules names available then that's what the documentation should say (even more so if the term "symbol table" hasn't been introduced yet, which would effectively render the entire block useless).
History
Date User Action Args
2013-03-08 16:02:29jeffknuppsetrecipients: + jeffknupp, ezio.melotti, eric.araujo, docs@python, ashwch, Piotr.Kuchta
2013-03-08 16:02:29jeffknuppsetmessageid: <1362758549.43.0.924067107884.issue17383@psf.upfronthosting.co.za>
2013-03-08 16:02:29jeffknupplinkissue17383 messages
2013-03-08 16:02:29jeffknuppcreate