[issue30842] pyenv activate for bash and tcsh

Vinay Sajip added the comment: If no PR is forthcoming for this, I'd like to close this issue as out of date. Any objections? -- ___ Python tracker ___ __

[issue30842] pyenv activate for bash and tcsh

Changes by Vinay Sajip : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue30842] pyenv activate for bash and tcsh

Arnon Sela added the comment: The procedure: pushd $fullpath fullpath=$(pwd -P) popd Can be made sh (and other shells) friendly by: here=$PWD # or $(pwd) cd $fullpath fullpath=$(pwd -P) cd $here More to write, but should work, right? -- __

[issue30842] pyenv activate for bash and tcsh

Vinay Sajip added the comment: Note that the activate script currently also works with /bin/sh (using . venv-dir/bin/activate) but pushd and popd are not supported there, and introducing them would presumably break this script on /bin/sh. -- ___ Pyt

[issue30842] pyenv activate for bash and tcsh

Arnon Sela added the comment: readlink -f can be replaced by the following sequence: pushd $fullpath fullpath=$(pwd -P) popd Please note that: [[ $called != $0 ]] && fullpath="${BASH_SOURCE[@]}" || fullpath=$0 Should be replaced with: [[ $called != $0 ]] && fullpath="${BA

[issue30842] pyenv activate for bash and tcsh

Vinay Sajip added the comment: This needs further thought as to how to implement. For example, readlink -f isn't supported on OS X. If a patch were available which works across platforms, that would potentially speed up resolution of this issue. --

[issue30842] pyenv activate for bash and tcsh

Arnon Sela added the comment: Thank you so much for considering this. Both windows and linux based systems provides mechanisms to be dynamic and relative to the path. I wish there would be a way to add such behavior to Python development manifesto and to check in pypi that packages are aligned

[issue30842] pyenv activate for bash and tcsh

Vinay Sajip added the comment: This seems reasonable, but scripts written to venvs by e.g. pip hard-code the path to the venv, and this is a stumbling block to relocatability. There is no reason to use the activate scripts except under interactive use - a script installed in a venv should be d

[issue30842] pyenv activate for bash and tcsh

Arnon Sela added the comment: Additional information: This suggestion will make pyenv much better. To emphasize the need, there are many places that due to security you cannot build virtualenv. Rather you have to push a virtualenv with your python code. Often enough, you also don't have con

[issue30842] pyenv activate for bash and tcsh

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue30842] pyenv activate for bash and tcsh

New submission from Arnon Sela: Remove hard coded path in activate family of virtualenv scripts. Currently, VIRTUAL_ENV is set hard coded. Event after --relocatable Instead, change to have is defined dynamically: E.g. bash: called=$_ [[ $called != $0 ]] && fullpath="${BASH_SOURCE[@]}" || ful