On Wed, Jan 13, 2010 at 9:40 AM, Ralf Schmitt <ralf at brainbot.com> wrote:
> "R. David Murray" <rdmurray at 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.
>>
>> [1] http://bugs.python.org/issue2375
>
> 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.
How complicated is your PYTHONSTARTUP file? My suspicion is that you
could easily write it to work for both Python 2.X and 3.X.
Steve
--
Where did you get that preposterous hypothesis?
Did Steve tell you that?
--- The Hiphopopotamus
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4