Changes between Version 1 and Version 2 of Ticket #61468, comment 3


Ignore:
Timestamp:
Nov 15, 2020, 7:19:15 PM (4 years ago)
Author:
smeingast (Stefan Meingast)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #61468, comment 3

    v1 v2  
    11Ah, I just discovered that I have this same problem with other ports as well. For instance 'sudo port select --set python python38' doesn't do the trick either anymore...
    22
    3 edit: I tried it both with bash and zsh, if that matters. no luck
     3edit: I tried it both with bash and zsh, if that matters. no luck.
     4
     5edit2: In general, there seems to be some inconsistency with respect to the select command:
     6
     7
     8{{{
     9port select --summary
     10Name       Selected       Options
     11====       ========       =======
     12cython     cython38       cython38 none
     13gcc        mp-gcc10       mp-gcc10 none
     14ipython    py38-ipython   py38-ipython none
     15ipython3   py38-ipython   py38-ipython none
     16nosetests  nosetests38    nosetests38 none
     17pip        pip38          pip3-apple pip38 none
     18python     python38       python27-apple python38 python38-apple none
     19python3    python38       python38 python38-apple none
     20}}}
     21
     22and then checking each with type:
     23
     24
     25
     26{{{
     27cython is /opt/local/bin/cython
     28gcc is /usr/bin/gcc
     29ipython is /opt/local/bin/ipython
     30ipython3 is /opt/local/bin/ipython3
     31nosetests is /opt/local/bin/nosetests
     32pip is /opt/local/bin/pip
     33python is /usr/bin/python
     34python3 is /usr/bin/python3
     35}}}
     36
     37As you can see, gcc, and the Python interpreters follow the wrong paths.
     38
     39