Opened 3 years ago
Closed 3 years ago
#64500 closed defect (fixed)
Selecting py310-ipython fails
Reported by: | ednl (Ewoud Dronkert) | Owned by: | lpsinger (Leo Singer) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | stromnov (Andrey Stromnov), smeingast (Stefan Meingast), ryandesign (Ryan Carsten Schmidt) | |
Port: | py-ipython |
Description
After seeing that python310 came as a dependency anyway, and after checking that all py39 ports I use were available as py310 versions, I tried switching to the 3.10 branch and first installed py310-ipython manually. That succeeded but selecting it with the suggested post-install command fails because 3.10/bin/iptest doesn't exist:
user@macmini:~$ sudo port select --set ipython3 py310-ipython Selecting 'py310-ipython' for 'ipython3' failed: could not create new link "/opt/local/bin/iptest3": target "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/iptest" doesn't exist user@macmini:~$ sudo port select --set ipython py310-ipython Selecting 'py310-ipython' for 'ipython' failed: could not create new link "/opt/local/bin/iptest": target "/opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/iptest" doesn't exist
This is on an M1 Mac mini.
Change History (8)
comment:1 Changed 3 years ago by ednl (Ewoud Dronkert)
comment:2 Changed 3 years ago by jmroot (Joshua Root)
Cc: | stromnov added |
---|---|
Keywords: | M1 removed |
Owner: | set to lpsinger |
Status: | new → assigned |
comment:4 Changed 3 years ago by smeingast (Stefan Meingast)
Cc: | smeingast removed |
---|
comment:5 Changed 3 years ago by smeingast (Stefan Meingast)
Cc: | smeingast added |
---|
comment:6 Changed 3 years ago by mfacorcoran
I have the same problem with py39-ipython on an intel mac/Big Sur
comment:7 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign added |
---|
comment:8 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
I guess it's a development test that was inadvertently not removed from the script? I ran this instead which is probably exactly what the script does (is supposed to do) :