#!/usr/bin/env python --> python3 where applicable
30 Apr
2009
30 Apr
'09
7:03 p.m.
Jared Grubb wrote:
Ok, so if I understand, the situation is: * python points to 2.x version * python3 points to 3.x version * need to be able to run certain 3k scripts from cmdline (since we're talking about shebangs) using Python3k even though "python" points to 2.x
So, if I got the situation right, then do these same scripts understand that PYTHONPATH and PYTHONHOME and all the others are also probably pointing to 2.x code?
Would it make sense to introduce PYTHON2PATH and PYTHON3PATH (or even PYTHON27PATH and PYTHON 32PATH) et al? Or is this an area where we just figure that whoever moved the file locations around for distribution can hardcode things properly? -jJ
5447
Age (days ago)
5447
Last active (days ago)
0 comments
1 participants
participants (1)
-
Jim Jewett