[MacPorts] #45130: Follow recommendation on Python commands
MacPorts
noreply at macports.org
Tue Sep 23 02:46:04 PDT 2014
#45130: Follow recommendation on Python commands
-------------------------+-------------------------------------------------
Reporter: | Owner: macports-dev@…
and.damore@… | Status: new
Type: enhancement | Milestone:
Priority: Normal | Version: 2.3.1
Component: ports | Port: python_select, python24, python25,
Keywords: python | python26, python27, python31, python32,
| python33, python34
-------------------------+-------------------------------------------------
With respect to [http://legacy.python.org/dev/peps/pep-0394/ The "python"
Command on Unix-Like Systems PEP] I'm proposing a patch to follow the
guidelines. It introduces python2 and python3 binaries in python ports'
selection files.
The PEP suggests that for now ''python'' command point to the same target
as python2.
This leads to an issue with current port selection feature:
if python34 has a "-" value for the corresponding "$prefix/bin/python2"
target in its select files entry it means that the "$prefix/bin/python2"
symlink gets removed when the port is selected.
What we would like instead is that the "$prefix/bin/python2" would be left
linking to an active python2X port, if there's any available, or should it
rather be left at system's python executable?
There's a more complicated case in which ports python26 and python27 are
both active and the system has to pick one. It could be handled by
selecting the most recent version but again this is could be against
user's specific needs.
Splitting the select groups in python2 and python3 wouldn't work well
since there would be an overlap of the common entries. There's somehow
need to mix the selections.
Any thought on this is welcome.
--
Ticket URL: <https://trac.macports.org/ticket/45130>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list