[Import-SIG] File based configuration for the import system
Antoine Pitrou
solipsis at pitrou.net
Tue Apr 26 11:08:29 EDT 2016
On Tue, 26 Apr 2016 12:19:04 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
>
> For me though, one of the other motivations behind the proposed changes in
> PEP 432 is getting to replace the current sys.path calculation code in
> getpath.c and getpathp.c with Python code in importlib._bootstrap or
> (depending on boot sequence details) importlib._bootstrap_external.
>
> Once we did that, there would be a range of ideas (like allowing additional
> path handling customisations in venv configuration files) that become
> significantly more feasible to implement and maintain.
>
> So, does that sound reasonable to folks as a revised primary motivation for
> that PEP: moving the default sys.path calculation code to Python for ease
> of reuse across implementations, and for ease of maintenance and
> enhancement within CPython itself?
Platonically, that sounds like a good idea, but obviously I'm not the
one doing the work (and good luck with the bootstrapping issues ;-)).
Regards
Antoine.
More information about the Import-SIG
mailing list