[Python-Dev] PEP 420 - dynamic path computation is missing rationale (original) (raw)

Brett Cannon brett at python.org
Wed May 23 21:56:07 CEST 2012

On Wed, May 23, 2012 at 3:35 PM, PJ Eby <pje at telecommunity.com> wrote:

On Wed, May 23, 2012 at 3:02 PM, Brett Cannon <brett at python.org> wrote:

If I understand the proposal correctly, this would be a change in NamespaceLoader in how it sets path and in no way affect any other code since import() just grabs the object on path and passes as an argument to the meta path finders which just iterate over the object, so I have no objections to it. That's not quite the proposal (but almost). The change would also mean that import() instead passes a ModulePath (aka Nick's LazyIterable) instance to the meta path finders, which just iterate over it. But other than that, yes.

And why does import() need to construct that? I thought NamespaceLoader was going to be making these "magical" path objects that detected changes and thus update themselves as necessary and just stick them on the object. Why specifically does import() need to play a role? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120523/527f8dfb/attachment.html>

More information about the Python-Dev mailing list