[issue30842] pyenv activate for bash and tcsh

2017-07-30 Thread Arnon Sela
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

2017-07-29 Thread Arnon Sela
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 !=

[issue30842] pyenv activate for bash and tcsh

2017-07-14 Thread Arnon Sela
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

2017-07-14 Thread Arnon Sela
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

[issue30842] pyenv activate for bash and tcsh

2017-07-03 Thread Arnon Sela
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="

[issue20353] Hanging bug with multiprocessing + sqlite3 + tkinter (OS X 10.9 only)

2015-04-04 Thread Arnon Sela
Arnon Sela added the comment: I ran into similar issue on OSX. Multiprocessing system where processes issue sqlite3.connect(). Periodically it hangs. System is using Python 3.4.3 and sqlite3; it doesn't use tkinter Noticed the following: 1. This doesn't happen on Ubuntu 2. It happens even