Antoine Pitrou wrote: > I am not sure when this discussion started. Are you replying to a 3 month-old > message of yours? :) That depends on how you define the beginning of the discussion... However, the fact that importlib doesn't implement the comparatively recent get_filename() optional extension documented in PEP 302 came up in one of the PEP 376 threads within the last week or so. > In any case, keeping all import-related ABCs in a single place sounds like a > good idea. > Alternatively, if the method is runpy specific, it doesn't have its place in an > ABC, does it? While runpy is the only client in the standard library for the get_filename() method, the method is still a PEP 302 extension. I documented the extension in the PEP as loaders are the only things reliably in a position to provide the filename details that runpy needs to set __file__ and sys.argv[0] correctly and until importlib came along PEP 302 itself was the only real documentation of that API. Since importlib is now the "go-to" location for people that want to write their own PEP 302 importers and loaders, I would say that it is also the right place for the new ExecutionLoader ABC. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4