[Python-Dev] PEP 420 - dynamic path computation is missing rationale (original) (raw)
PJ Eby pje at telecommunity.com
Wed May 23 21:35:28 CEST 2012
- Previous message: [Python-Dev] PEP 420 - dynamic path computation is missing rationale
- Next message: [Python-Dev] PEP 420 - dynamic path computation is missing rationale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120523/a2e874c2/attachment.html>
- Previous message: [Python-Dev] PEP 420 - dynamic path computation is missing rationale
- Next message: [Python-Dev] PEP 420 - dynamic path computation is missing rationale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]