Opened 11 years ago
Closed 10 years ago
#42747 closed enhancement (duplicate)
"port python --select" should offer "python3" and "python2" options
| Reported by: | ned-deily (Ned Deily) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.1 |
| Keywords: | Cc: | jyrkiwahlstedt, cooljeanius (Eric Gallager) | |
| Port: | python_select |
Description
As documented in Python PEP 394 (http://legacy.python.org/dev/peps/pep-0394/), it is problematic and not currently recommended to use "python" as a synonym for a Python 3 version. Recommended upstream practice is to offer "python3' as a synonym for the current preferred Python 3 version, "python2" for the current preferred Python 2 version, and, during the long transition period from Python 2 to Python 3, recommend "python" be the same as "python2" but eventually moving to "python3". In support of this, "port select --python" should support "python3" and "python2" groups.
Change History (3)
comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)
| Cc: | egall@… added |
|---|
comment:2 Changed 11 years ago by J.Gilbey@…
Yes, I just got bitten by this one too: there are python programs written in Python 3.x which begin with #! /usr/bin/env python3, which won't run under macports because there's no python3 symlink :-(
comment:3 Changed 10 years ago by larryv (Lawrence Velázquez)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Consolidating into #34326.
Cc Me!