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 barry
Recipients barry, brett.cannon, eric.araujo, eric.snow, georg.brandl, larry, ncoghlan, skrah
Date 2012-07-31.14:03:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120731100305.130fce9d@limelight.wooz.org>
In-reply-to <1343538647.87.0.343802121082.issue15295@psf.upfronthosting.co.za>
Content
On Jul 29, 2012, at 05:10 AM, Nick Coghlan wrote:

>I would title the new section "Import system" rather than "Import machinery"
>as it is meant to be a specification documentation rather than an
>implementation description.

"Import system" it is.

>The statement that "from X import A" only performs a single import lookup is
>incorrect. The trick is that if A, B or C refers to a submodule of X then it
>will be imported.

I think I see where you and Eric are coming from on this.  Actually, I don't
think I changed the existing text in this regard, but probably once I
refactored out all the details, it reads in such a way as to be confusing.
I've tweaked the text under the import statement to hopefully be more clear.
It could probably still use improvement.
History
Date User Action Args
2012-07-31 14:03:07barrysetrecipients: + barry, brett.cannon, georg.brandl, ncoghlan, larry, eric.araujo, skrah, eric.snow
2012-07-31 14:03:06barrylinkissue15295 messages
2012-07-31 14:03:05barrycreate