This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | glyph |
|---|---|
| Recipients | glyph |
| Date | 2008年03月18日.00:34:08 |
| SpamBayes Score | 0.344923 |
| Marked as misclassified | No |
| Message-id | <1205800495.39.0.697300117462.issue2375@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Currently if you have both Python 3 and Python 2 installed, there's no way to indicate that ".py" files in one area are Python 2 syntax and in another area are Python 3 syntax. Being able to distinguish between these would be nice for heterogeneous deployment environments, but is particularly important for developers who are working on Python 3 conversions. It would be good to have a PYTHON3PATH which, if present, would be honored instead of PYTHONPATH. PYTHONPATH could still be honored if PYTHON3PATH was not present, so this is purely a new feature and shouldn't have much impact on compatibility. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月18日 00:34:55 | glyph | set | spambayes_score: 0.344923 -> 0.344923 recipients: + glyph |
| 2008年03月18日 00:34:55 | glyph | set | spambayes_score: 0.344923 -> 0.344923 messageid: <1205800495.39.0.697300117462.issue2375@psf.upfronthosting.co.za> |
| 2008年03月18日 00:34:08 | glyph | link | issue2375 messages |
| 2008年03月18日 00:34:08 | glyph | create | |