[Python-Dev] PEP 405 (pyvenv) and system Python upgrades (original) (raw)
Paul Moore p.f.moore at gmail.com
Tue May 8 19:34:09 CEST 2012
- Previous message: [Python-Dev] PEP 405 (pyvenv) and system Python upgrades
- Next message: [Python-Dev] The step command of pdb is broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8 May 2012 17:14, Carl Meyer <carl at oddbird.net> wrote:
I don't think anyone has proposed making symlinks the default on Windows. At this point the two options on Windows would be to use the --symlink option explicitly, or else to need to run "pyvenv --upgrade" on your envs if you upgrade the underlying Python in-place (and there's a breaking incompatibility between the new stdlib and the old interpreter, which there almost never will be if the past is any indication).
I expect most users will opt for the latter option (equivalent to how current virtualenv works, except virtualenv doesn't have an --upgrade flag so you have to upgrade manually), but the former is also available if some prefer it. In any case, the situation will be no worse than it is with virtualenv today.
That sounds fine. I apologise - I'd got the impression that the proposal was to make symlinks the default.
Paul.
- Previous message: [Python-Dev] PEP 405 (pyvenv) and system Python upgrades
- Next message: [Python-Dev] The step command of pdb is broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]