On Jan 13, 2010, at 12:40 PM, Ralf Schmitt wrote:
"R. David Murray" <rdmurray@bitdance.com> writes:
Please review issue 2375 [1], which is an enhancement request to add a PYTHON3PATH environment variable. Because we have elected to have both a python and a python3 command, I think this is an issue worth thinking about carefully to make sure we are serving the Python user community and easing the transition to python3. It could be that "use virtualenv" is the best answer, but I feel we should think about it carefully to make sure that is really true.
The first thing I got while trying to run a python3 prompt few days ago, was an error. python3 tried to read my $PYTHONSTARTUP file, which used print statements. people will have to run both python 2 and python 3 code at the same time. Using different environment variables will make this easier.
Or, how about just removing the antiquated use of environment variables altogether from Python 3 and avoid the issue completely. Python 2 will continue to run as it has, and better solutions will emerge for Python 3 development. Beats the heck out of making a whole duplicate set for PYTHON3BLAHBLAH, yuck! S