[Python-Dev] PEP 405 (built-in virtualenv) status
Ethan Furman
ethan at stoneleaf.us
Mon Mar 19 21:42:57 CET 2012
More information about the Python-Dev mailing list
Mon Mar 19 21:42:57 CET 2012
- Previous message: [Python-Dev] PEP 405 (built-in virtualenv) status
- Next message: [Python-Dev] PEP 405 (built-in virtualenv) status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carl Meyer wrote: > The bulk of the work in PEP 405 is aimed towards a rather different goal > from yours - to be able to share an installed Python's copy of the > standard library among a number of virtual environments. This is the > purpose of the "home" key in pyvenv.cfg and the added sys.base_prefix > (which point to the Python installation whose standard library will be > used). I think this serves a valuable and common use case, but I wonder > if your use case couldn't also be served with a minor tweak to PEP 405. > Currently it ignores a pyvenv.cfg file with no "home" key; instead, it > could set sys.prefix and sys.base_prefix both to the location of that > pyvenv.cfg. For most purposes, this would result in a broken Python (no > standard library), but it might help you? Instead of no home key, how about an empty home key? Explicit being better, and all that. ~Ethan~
- Previous message: [Python-Dev] PEP 405 (built-in virtualenv) status
- Next message: [Python-Dev] PEP 405 (built-in virtualenv) status
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list