[sage-support] Re: Sage Crash Report
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.
[sage-support] Re: Sage Crash Report
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/47d05f44-1757-422d-87e5-6c5998580ea9n%40googlegroups.com.
[sage-support] Re: Sage Crash Report
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/f7acfe71-e5ea-4a46-afee-cc333f371222n%40googlegroups.com.
[sage-support] Sage Crash Report
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/CABdAJe%2BGEhGwML%2BO%2BVVqKsNkCPNBt5pmqPMssETzUnif__8q5Q%40mail.gmail.com.
***
IPython post-mortem report
{'commit_hash': '223e783c4',
'commit_source': 'installation',
'default_encoding': 'utf-8',
'ipython_path':
'/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython',
'ipython_version': '7.19.0',
'os_name': 'posix',
'platform': 'macOS-10.16-x86_64-i386-64bit',
'sys_executable': '/opt/miniconda3/envs/sage/bin/python',
'sys_platform': 'darwin',
'sys_version': '3.8.5 | packaged by conda-forge | (default, Sep 24 2020, '
'16:37:41) \n'
'[Clang 10.0.1 ]'}
***
***
Crash traceback:
---
---
TypeErrorPython 3.8.5: /opt/miniconda3/envs/sage/bin/python
Mon Jan 4 14:16:47 2021
A problem occurred executing Python code. Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/terminal/ptutils.py
in get_completions(self=,
document=Document('cd Do', 5),
complete_event=CompleteEvent(text_inserted=False, completion_requested=True))
112 try:
--> 113 yield from self._get_completions(body, offset,
cursor_position, self.ipy_completer)
self._get_completions =
body = 'cd Do'
offset = 5
cursor_position = 5
self.ipy_completer =
114 except Exception as e:
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/terminal/ptutils.py
in _get_completions(body='cd Do', offset=5, cursor_position=5,
ipyc=)
128 body, ipyc.completions(body, offset))
--> 129 for c in completions:
c = undefined
completions =
130 if not c.text:
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/core/completer.py
in _deduplicate_completions(text='cd Do', completions=)
437 """
--> 438 completions = list(completions)
completions =
global list = undefined
439 if not completions:
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/core/completer.py
in completions(self=, text='cd Do',
offset=5)
1817 try:
-> 1818 for c in self._completions(text, offset,
_timeout=self.jedi_compute_type_timeout/1000):
c = undefined
self._completions = >
text = 'cd Do'
offset = 5
global _timeout = undefined
self.jedi_compute_type_timeout = 400
1819 if c and (c in seen):
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/core/completer.py
in _completions(self=, full_text='cd
Do', offset=5, _timeout=0.4)
1860
-> 1861 matched_text, matches, matches_origin, jedi_matches =
self._complete(
matched_text = undefined
matches = undefined
matches_origin = undefined
jedi_matches = undefined
self._complete = >
full_text = 'cd Do'
cursor_line = 0
global cursor_pos = undefined
cursor_column = 5
1862 full_text=full_text, cursor_line=cursor_line,
cursor_pos=cursor_column)
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/core/completer.py
in _complete(self=, cursor_line=0,
cursor_pos=5, line_buffer='cd Do', text='Do', full_text='cd Do')
2028 full_text = line_buffer
-> 2029 completions = self._jedi_matches(
completions = ()
self._jedi_matches = >
cursor_pos = 5
cursor_line = 0
full_text = 'cd Do'
2030 cursor_pos, cursor_line, full_text)
/opt/miniconda3/envs/sage/lib/python3.8/site-packages/IPython/core/completer.py
in _jedi_matches(self=,
cursor_column=5, cursor_line=0, text='cd Do')
1372
-> 1373 interpreter = jedi.Interpreter(
interpreter = undefined
