Re: PEP 420 issue: extend_path
Nick Coghlan <[email protected]>
| Newsgroups | gmane.comp.python.import |
|---|---|
| Message-ID | <CADiSq7ehe4i+Eedbfs6GSsKukCz5ja_LdLv+RS9WVPXj59m5Zg@mail.gmail.com> |
On May 8, 2012 2:21 AM, "Antoine Pitrou" <[email protected]> wrote: > > In any case, do note that returning something else than either a loader > or None already breaks the API, AFAICT. Existing code calling > find_module() will have to be adapted... Which is perhaps worse than > the perceived migration problem in PEP 382. 382 would have had the same problem. Given that sys.path already holds strings, as do __path__ attributes, I don't see any value in adding a separate PathEntry type just for signalling purposes. However, I do think we need to give more thought to allowing old finders to gracefully degrade by reporting "not found" instead of throwing an error. Will write more on that when I get to a real computer :) -- Sent from my phone, thus the relative brevity :) _______________________________________________ Import-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/import-sig