Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2009-April/089291.html below:

[Python-Dev] #!/usr/bin/env python --> python3 where applicable

• Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• Next message: [Python-Dev] 3.1 beta deferred
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

• Previous message: [Python-Dev] PEP 383: Non-decodable Bytes in System Character Interfaces
• Next message: [Python-Dev] 3.1 beta deferred
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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