I searched for "ipython-5.0.0" in the source and found this:
if [ -z "$IPYTHONDIR" ]; then
# We hardcode a version number in the directory name. The idea is
# that we keep using the same version number as long as that is
# possible. Only when some future IPython version really
The problem that it *causes* is that people think that Sage has somehow
managed to install an ancient ipython-5.0.0 in their ~/.sage directory.
The user that reported this was indeed having problems because of an out of
date ipython thet they had installed with %pip. The python package was
One scenario where I could see this being beneficial:
These configurations are written into `$HOME/.sage` (normally), so that is
not a location that is predicated by a venv or a localized subdir. If a
user is using two different sagemath installs (e.g., one system, the other
for development)
On 31 March 2024 15:23:24 CEST, Marc Culler wrote:
>This is a follow-up to a user's query in a Sage_macOS issue.
>
>The current sage-env script contains the excerpt below. It seems pretty
>confusing that Sage would create a directory named .sage/ipython-5.0.0
>when Sage is shipping
This is a follow-up to a user's query in a Sage_macOS issue.
The current sage-env script contains the excerpt below. It seems pretty
confusing that Sage would create a directory named .sage/ipython-5.0.0
when Sage is shipping IPython 8.18.1. What would be wrong with calling the
directory
