[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

Vinay Sajip added the comment: Indeed, and in fact *all* scripts written to a venv's bin directory hard-code the path to that venv's interpreter. This confers the benefit that such scripts never need the venv to be explicitly activated - you can e.g. point crontab entries to them directly.

[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

Changes by André Caron : -- nosy: +André Caron ___ Python tracker ___ ___

[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

New submission from Chad Moore: venv/bin/activate contains an absolute path to the virtual environment. Is it possible to make that relative from activate itself so that the entire venv can be moved elsewhere and still work? I found this using Jenkins to get a Perforce workspace, then build

[issue25833] pyvenv: venvs cannot be moved because activate scripts hard-code paths

R. David Murray added the comment: It's been that way since the virtualenv days, and I presume there's a reason for it. virtualenv does have a '--relocatable' option, but it is still marked as experimental. Finding out why that is and addressing the issues would be a prerequisite for adding