On Friday, May 26, 2017 at 7:52:57 AM UTC-7, John H Palmieri wrote: > > If you build Sage's IPython package with SAGE_PYTHON3=yes, then it will > install a script local/bin/ipython3. (Note then that if the sage-location > script runs, its function make_scripts_relative will break > local/bin/ipython3 because it will replace the #! line, which initially > uses Sage's Python3, to a generic /usr/bin/env python. Another broken part > to fix.) >
Ah, that would explain it. Data point on naming: on my fedora25, there are /usr/bin/ipython, /usr/bin/ipython2, /usr/bin/python3 (each separate files). ipython and ipython3 are identical. The ipython2 might be a historical remnant, though. For Python, there are /usr/bin/python2.7, /usr/bin/python3.5 with /usr/bin/python a symlink pointing to /usr/bin/python2.7 (via some other symlinks). So there seems to be precedent that the naming convention for "python" does not translate to naming convention for "ipython". In any case, I think it would be good to ensure we at least have functioning *python2* and *python3* links. What the unnumbered names refer to is then slightly less vital. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
