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 a virtual environment, and clone that for downstream jobs. The cloned workspaces are extracted elsewhere and when they activate the environment they're actually pointing back to the upstream job's venv. Feel free to route this request as appropriate. I'm a new tracker user. Thanks! ---------- components: Library (Lib) messages: 256176 nosy: moorecm priority: normal severity: normal status: open title: pyvenv: venvs cannot be moved because activate scripts hard-code paths versions: Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25833> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
