[MacPorts] #38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed ----------------------------------+---------------------------------------- Reporter: | Owner: macports-tickets@… macports.jgonggrijp@… | Status: new Type: defect | Milestone: Priority: Normal | Version: 2.1.3 Component: ports | Port: python32 python33 python31 Keywords: | ----------------------------------+---------------------------------------- I have python26, python27 and python32 installed on Mac OS X 10.6.8 with Xcode 3.2.6. Normally when Python 2 and Python 3 are installed alongside on a unixy system there should be both a python2 link and a python3 link, as detailed in PEP 394: http://www.python.org/dev/peps/pep-0394/ MacPorts does indeed install a python2 command, but no python3 command. This is what I get when I run {{{ls /opt/local/bin/python*}}}: {{{ /opt/local/bin/python /opt/local/bin/python2.6-config /opt/local/bin/pythonw /opt/local/bin/python-config /opt/local/bin/python2.7 /opt/local/bin/pythonw2 /opt/local/bin/python2 /opt/local/bin/python2.7-config /opt/local/bin/pythonw2.6 /opt/local/bin/python2-config /opt/local/bin/python3.2 /opt/local/bin/pythonw2.7 /opt/local/bin/python2.6 /opt/local/bin/python3.2-config /opt/local/bin/pythonw3.2 }}} Usually I have python27 selected as the default version, but changing that setting to python32 does not change the above directory listing. This may also affect other python3x ports; I haven't checked whether that is the case. Somewhat related: ticket [ticket:34326]. -- Ticket URL: <https://trac.macports.org/ticket/38661> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Changes (by jmr@…): * cc: raimue@… (added) * port: python32 python33 python31 => python_select python32 python33 python31 Comment: I think the python2 and python3 links should really be managed by port select. Where does your existing python2 link point to, BTW? -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by macports.jgonggrijp@…): python2 points to python2.7. I think the python2 and python3 links should both exist regardless of what version is selected as the default. The Python versions are installed in parallel for a reason; you want to be able to run both and be able to (portably) indicate which one for example in a shebang line. See the PEP for a full rationale. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by larryv@…): Replying to [comment:3 macports.jgonggrijp@…]:
I think the python2 and python3 links should both exist regardless of what version is selected as the default.
I would assume that the `python2` and `python3` select groups would be independent of the `python` select group. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by macports.jgonggrijp@…):
I would assume that the `python2` and `python3` select groups would be independent of the `python` select group.
Well, that would certainly be nice. I guess this is what jmr meant, sorry for being dense. ;) Though as far as portability (and the PEP) is concerned, it's sufficient if each link points to the latest corresponding version that is installed. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by g5pw@…): Anyone already working on this? I can give a shot at splitting {{{python_select}}} into {{{python{2,3}_select}}}. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by larryv@…): Replying to [comment:7 g5pw@…]:
Anyone already working on this? I can give a shot at splitting {{{python_select}}} into {{{python{2,3}_select}}}.
I’m not sure we want to get rid of the `python` select group. Adding `python2` and `python3` is probably fine, though. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by g5pw@…): Replying to [comment:8 larryv@…]:
I’m not sure we want to get rid of the `python` select group. Adding `python2` and `python3` is probably fine, though.
Why not? I don't suggest removing it completely, but splitting it two select groups. Then we just have to figure out how to select %prefix/bin/python. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by larryv@…): Replying to [comment:9 g5pw@…]:
Replying to [comment:8 larryv@…]:
I’m not sure we want to get rid of the `python` select group. Adding `python2` and `python3` is probably fine, though.
Why not? I don't suggest removing it completely, but splitting it two select groups. Then we just have to figure out how to select %prefix/bin/python.
I’m not sure what you mean. My thought is that we’d have three groups—“python”, “python2”, and “python3”—all set independently of each other. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Resolution: | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Comment (by guillaume.salagnac@…): Cc me -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X
#38661: python32 @3.2.3 doesn't create a python3 link while python2 is installed -------------------------------------------------+------------------------- Reporter: macports.jgonggrijp@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: closed Component: ports | Milestone: Resolution: duplicate | Version: 2.1.3 Port: python_select python32 python33 | Keywords: python31 | -------------------------------------------------+------------------------- Changes (by larryv@…): * status: new => closed * resolution: => duplicate Comment: Consolidating into #34326. -- Ticket URL: <https://trac.macports.org/ticket/38661#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts