Message 205927 - Python tracker

➜

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	Arfrever, brett.cannon, eric.snow, ncoghlan
Date	2013-12-11.21:31:09
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CADiSq7dya0+dqrDNvqQaP03fNEh1m-A5AkBe+Am8ehTFkmCwpw@mail.gmail.com>
In-reply-to	<1386772850.53.0.934686698105.issue19944@psf.upfronthosting.co.za>

Content
Look at it from a conceptual point of view, though, there are two quite different operations: - find a spec at the current level, using the specified path (which may be empty, implying a top level import) - find a spec according to the full import cycle, including any parent module imports When you call it, you're going to want one behaviour or the other, since the two operations are not slight variants, they have major conceptual differences (with one being a substep of the other).

Look at it from a conceptual point of view, though, there are two quite
different operations:

- find a spec at the current level, using the specified path (which may be
empty, implying a top level import)
- find a spec according to the full import cycle, including any parent
module imports

When you call it, you're going to want one behaviour or the other, since
the two operations are not slight variants, they have major conceptual
differences (with one being a substep of the other).

History
Date	User	Action	Args
2013-12-11 21:31:09	ncoghlan	set	recipients: + ncoghlan, brett.cannon, Arfrever, eric.snow
2013-12-11 21:31:09	ncoghlan	link	issue19944 messages
2013-12-11 21:31:09	ncoghlan	create