[MacPorts] #56278: Automatically include /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[MacPorts] #56278: Automatically include /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH

MacPorts
#56278: Automatically include
/opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH
-------------------------+--------------------
 Reporter:  l-g          |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:
-------------------------+--------------------
 I just installed some utilities using pip from MacPorts and was surprised
 that I didn't have access to them automatically/after a rehash/in a new
 terminal.

 Wouldn't it make sense to include
 ./opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/pip3.4
 and similar directories in $PATH when they are created? Should be simple
 to include the relevant commands in the portfile.

--
Ticket URL: <https://trac.macports.org/ticket/56278>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #56278: Automatically include /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH

MacPorts
#56278: Automatically include
/opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH
--------------------------+--------------------
  Reporter:  l-g          |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by ryandesign):

 MacPorts ports don't modify the user's path. Only the MacPorts installer
 modifies the user's path, and then only to add /opt/local/bin and
 /opt/local/sbin.

--
Ticket URL: <https://trac.macports.org/ticket/56278#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #56278: py-pip: Does not install ${prefix}/bin/pipX.Y (was: Automatically include /opt/local/Library/Frameworks/Python.framework/Versions/3.4/bin/ into $PATH)

MacPorts
In reply to this post by MacPorts
#56278: py-pip: Does not install ${prefix}/bin/pipX.Y
---------------------+----------------------
  Reporter:  l-g     |      Owner:  stromnov
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:
      Port:  py-pip  |
---------------------+----------------------
Changes (by raimue):

 * owner:  (none) => stromnov
 * status:  new => assigned
 * type:  enhancement => defect
 * port:   => py-pip


Comment:

 As MacPorts provides multiple versions of python, these tools inherently
 conflict. Therefore they are usually installed with the appropriate
 version suffix into `/opt/local/bin`.

 There should be a symlink at `/opt/local/bin/pip3.4`. But apparently there
 is not, so this is a bug with the py-pip port.

 See also the notes for python34 and related ports on how to make this
 version the default:

 {{{
 $ port notes python34
 python34 has the following notes:
   To make this the default Python or Python 3 (i.e., the version run by
 the 'python' or 'python3' commands), run one
   or both of:

       sudo port select --set python python34
       sudo port select --set python3 python34
 }}}
 {{{
 $ port notes py34-pip
 py34-pip has the following notes:
   To make the Python 3.4 version of pip the one that is run when you
 execute the commands without a version suffix,
   e.g. 'pip', run:

   port select --set pip pip34
 }}}

--
Ticket URL: <https://trac.macports.org/ticket/56278#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #56278: py-pip: Does not install ${prefix}/bin/pipX.Y

MacPorts
In reply to this post by MacPorts
#56278: py-pip: Does not install ${prefix}/bin/pipX.Y
---------------------+----------------------
  Reporter:  l-g     |      Owner:  stromnov
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:
      Port:  py-pip  |
---------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:2 raimue]:
 > There should be a symlink at `/opt/local/bin/pip3.4`. But apparently
 there is not, so this is a bug with the py-pip port.

 There is a symlink /opt/local/bin/pip-3.4. So there is no bug.

--
Ticket URL: <https://trac.macports.org/ticket/56278#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #56278: py-pip: Does not install ${prefix}/bin/pipX.Y

MacPorts
In reply to this post by MacPorts
#56278: py-pip: Does not install ${prefix}/bin/pipX.Y
----------------------+----------------------
  Reporter:  l-g      |      Owner:  stromnov
      Type:  defect   |     Status:  closed
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:  invalid  |   Keywords:
      Port:  py-pip   |
----------------------+----------------------
Changes (by raimue):

 * status:  assigned => closed
 * resolution:   => invalid


Comment:

 Fair enough, I would have expected it to follow the naming scheme of
 pythonX.Y, but both types of suffixes (`X.Y` and `-X.Y`) exist in various
 ports... Then there really is no bug in py-pip.

--
Ticket URL: <https://trac.macports.org/ticket/56278#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS