Glad I can help. This is another reason why these virtual environments are
really useful! I have one environment for sage which I never try to update
since I know that everything works. Separately, I have my "main"
environment that I update regularly, which will occasionally break things.
I broke ipython in that environment and then stumbled
on https://github.com/ipython/ipython/issues/12740 which tracks this
problem.
You can also feel free to experiment without fear of breaking things using
conda. For example, I see that you have sage installed with python 3.8.
If you wanted to try sage with python 3.9 without any fear you could do
something like
conda create -n sage_python3.9 sage=9.2 python=3.9 -c conda-forge
and then you would have a new environment with sage 9.2 and python 3.9.
Given how often Mac's new operating systems break everything, it's kind of
amazing that conda has been so stable. A lot of credit goes to Isuru
Fernando and the work that he puts in on maintaining sage on conda forge.
On Monday, January 4, 2021 at 12:58:09 PM UTC-5 maciek...@gmail.com wrote:
> ad. 1. It turned out that indeed I had installed the most recent version
> of jedi. Installing 0.17.2 fixed the problem - thank you very much!
>
> ad. 2. I see - I am new to conda and I only used it to install sage;
> thanks for your explanation.
>
> On Monday, January 4, 2021 at 6:38:01 PM UTC+1 zsc...@gmail.com wrote:
>
>> 1. Did you by any chance accidentally update the jedi package? This is
>> not really a sage problem, but ipython 7.19.0 is incompatible with the most
>> recent version of jedi 0.18.0. In your sage environment you can run "conda
>> list" to see what packages you have installed. If jedi 0.18.0 is listed
>> then you can run "conda install jedi==0.17.2".
>>
>> 2. That's kinda the whole point behind anaconda/miniconda. You can put
>> different python projects into different environments so that their
>> dependencies don't contaminate one another. If you want to have your sage
>> environment always loaded you can activate it in your .zshrc file or you
>> can do something like
>>
>> >> alias sage="whatever your path to the conda sage binary is".
>>
>> On Monday, January 4, 2021 at 8:48:28 AM UTC-5 maciek...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> I encountered the following problems with sage:
>>>
>>> 1. It crashes when I am using tab auto completion - report attached.
>>> 2. Each time I want to use sage (by command 'sage') after restarting the
>>> system I need to type 'conda activate sage'. Otherwise command sage is
>>> not recognized ('-bash: sage: command not found').
>>>
>>> I run Sage 9.2 on MacOS Big Sur 11.1 (Macbook Pro) which was installed
>>> by Conda.
>>>
>>> Best,
>>> Maciek
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-support/d261b6be-8ca6-417e-bcdc-0647ac9a53cdn%40googlegroups.com.
