[sage-release] Re: Sage 9.8.beta7 released

[John H Palmieri]

Patch available: https://trac.sagemath.org/ticket/34935


On Tuesday, January 24, 2023 at 2:47:15 PM UTC-8 John H Palmieri wrote:

> I think Matthias found the answer in the emacs-lisp code (discussion at 
> https://trac.sagemath.org/ticket/34547#comment:56).
>
> On Tuesday, January 24, 2023 at 2:31:38 PM UTC-8 emanuel.c...@gmail.com 
> wrote:
>
>> I have absolutely no idea why this change would make a difference…
>>
>> The explanation is probably in sahe-shell-mode emacs-lisp code, 
>> originally written by someone wose emacs-lisp fu is widely heavier than 
>> mine.
>>
>> sage-shell-mode code, as far as I know, isn’t understood by nobodu, 
>> since its original author went to greener pas$tures… A concerted effort to 
>> understand and *comment* it might be worthwile… 
>> ​
>> Le mardi 24 janvier 2023 à 23:15:40 UTC+1, John H Palmieri a écrit :
>>
>>> For reasons I really don't understand, removing these lines from 
>>> sage.interfaces.all seem to have caused this:
>>>
>>> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
>>> -  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
>>> -  'mathematica', 'mwrank', 'octave', 'r', \
>>> -  'singular', 'sage0', 'sage']
>>>
>>> At least if I restore those lines, or even just add a line "interfaces = 
>>> []", then emacs appears to work again. I haven't tried it very much, though.
>>>
>>> I have absolutely no idea why this change would make a difference...
>>>
>>>
>>> On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de 
>>> wrote:
>>>
 I tried to comment out all the changes in all_cmdline.py, but this 
 didn't help.  The diff of src/sage/interfaces/all.py is a bit unclear to 
 me, I don't see what could be a problem there. 

 On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:

> This was one of my guesses because that ticket could have changed 
> global behavior of Sage by changing some imports — most of the tickets 
> made 
> more focused changes. Can you start with 9.8.beta6 and just apply some of 
> the changes from #34547? In particular, do things work if you don't 
> include 
> the changes in all_cmdline.py?
>
> -- 
> John
>
>
> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de 
> wrote:
>
>> I just spent some time to debug this, but I failed.  The problem 
>> seems to be that sage-shell:wait-for-redirection-to-complete in 
>> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>>  
>> does not return.  There is only one python file involved, 
>> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
>>  
>> but I do not see what #34547 has to do with it.  Something about 
>> lazy_import maybe?
>>
>> I can see that in sage-shell:run-cell-raw-output the command
>>
>> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>>  
>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>>
>> was sent to the process (using process-send-string), and after that,
>>
>> (sage-shell:wait-for-redirection-to-complete)
>>
>> never returns.  I don't know how to debug the python code, 
>> unfortunately.  Most importantly, I don't see what changed - what does 
>> #34547 have to do with it?
>>
>> Martin
>>
>>
>>
>> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>>
>>> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems 
>>> that #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
>>> Not sure where to go from here.  Should I open a ticket on trac?
>>>
>>> For me personally, this is a blocker, but I have no idea how many 
>>> emacs users there are.
>>>
>>> Martin
>>>
>>>
>>> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de 
>>> wrote:
>>>
 Thank you for this suggestion!  I will try with 9.8.beta6 + 
 #33842.  I hope that all dependencies are in the branch.

 Martin

 On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:

> Could it be #34547, #16522, or #33842? I'm just taking guesses 
> based on the newly merged tickets.
>
> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 
> emanuel.c...@gmail.com wrote:
>
>> From someone called mantepse in the sage-shell-mode 
>> 
>>  issue 
>> on github :
>>
>> ```
>> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 
>> build. Apparently, if I first 

[sage-release] Re: Sage 9.8.beta7 released

[John H Palmieri]

I think Matthias found the answer in the emacs-lisp code (discussion at 
https://trac.sagemath.org/ticket/34547#comment:56).

On Tuesday, January 24, 2023 at 2:31:38 PM UTC-8 emanuel.c...@gmail.com 
wrote:

> I have absolutely no idea why this change would make a difference…
>
> The explanation is probably in sahe-shell-mode emacs-lisp code, 
> originally written by someone wose emacs-lisp fu is widely heavier than 
> mine.
>
> sage-shell-mode code, as far as I know, isn’t understood by nobodu, since 
> its original author went to greener pas$tures… A concerted effort to 
> understand and *comment* it might be worthwile… 
> ​
> Le mardi 24 janvier 2023 à 23:15:40 UTC+1, John H Palmieri a écrit :
>
>> For reasons I really don't understand, removing these lines from 
>> sage.interfaces.all seem to have caused this:
>>
>> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
>> -  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
>> -  'mathematica', 'mwrank', 'octave', 'r', \
>> -  'singular', 'sage0', 'sage']
>>
>> At least if I restore those lines, or even just add a line "interfaces = 
>> []", then emacs appears to work again. I haven't tried it very much, though.
>>
>> I have absolutely no idea why this change would make a difference...
>>
>>
>> On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de wrote:
>>
>>> I tried to comment out all the changes in all_cmdline.py, but this 
>>> didn't help.  The diff of src/sage/interfaces/all.py is a bit unclear to 
>>> me, I don't see what could be a problem there. 
>>>
>>> On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>>>
 This was one of my guesses because that ticket could have changed 
 global behavior of Sage by changing some imports — most of the tickets 
 made 
 more focused changes. Can you start with 9.8.beta6 and just apply some of 
 the changes from #34547? In particular, do things work if you don't 
 include 
 the changes in all_cmdline.py?

 -- 
 John


 On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de 
 wrote:

> I just spent some time to debug this, but I failed.  The problem seems 
> to be that sage-shell:wait-for-redirection-to-complete in 
> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>  
> does not return.  There is only one python file involved, 
> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
>  
> but I do not see what #34547 has to do with it.  Something about 
> lazy_import maybe?
>
> I can see that in sage-shell:run-cell-raw-output the command
>
> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>  
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>
> was sent to the process (using process-send-string), and after that,
>
> (sage-shell:wait-for-redirection-to-complete)
>
> never returns.  I don't know how to debug the python code, 
> unfortunately.  Most importantly, I don't see what changed - what does 
> #34547 have to do with it?
>
> Martin
>
>
>
> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>
>> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems 
>> that #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
>> Not sure where to go from here.  Should I open a ticket on trac?
>>
>> For me personally, this is a blocker, but I have no idea how many 
>> emacs users there are.
>>
>> Martin
>>
>>
>> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  
>>> I hope that all dependencies are in the branch.
>>>
>>> Martin
>>>
>>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>>
 Could it be #34547, #16522, or #33842? I'm just taking guesses 
 based on the newly merged tickets.

 On Monday, January 23, 2023 at 10:42:37 AM UTC-8 
 emanuel.c...@gmail.com wrote:

> From someone called mantepse in the sage-shell-mode 
> 
>  issue 
> on github :
>
> ```
> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 
> build. Apparently, if I first use the beta6 one for sage-shell-mode, 
> I can 
> then use beta7 in the same emacs session.
> ```
>
> I don't get it either...
>
> There are two short Python files in the current `sahe-shell-mode` 
> 

[sage-release] Re: Sage 9.8.beta7 released

[Emmanuel Charpentier]

 

I have absolutely no idea why this change would make a difference…

The explanation is probably in sahe-shell-mode emacs-lisp code, originally 
written by someone wose emacs-lisp fu is widely heavier than mine.

sage-shell-mode code, as far as I know, isn’t understood by nobodu, since 
its original author went to greener pas$tures… A concerted effort to 
understand and *comment* it might be worthwile… 
​
Le mardi 24 janvier 2023 à 23:15:40 UTC+1, John H Palmieri a écrit :

> For reasons I really don't understand, removing these lines from 
> sage.interfaces.all seem to have caused this:
>
> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
> -  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
> -  'mathematica', 'mwrank', 'octave', 'r', \
> -  'singular', 'sage0', 'sage']
>
> At least if I restore those lines, or even just add a line "interfaces = 
> []", then emacs appears to work again. I haven't tried it very much, though.
>
> I have absolutely no idea why this change would make a difference...
>
>
> On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de wrote:
>
>> I tried to comment out all the changes in all_cmdline.py, but this didn't 
>> help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I 
>> don't see what could be a problem there. 
>>
>> On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>>
>>> This was one of my guesses because that ticket could have changed global 
>>> behavior of Sage by changing some imports — most of the tickets made more 
>>> focused changes. Can you start with 9.8.beta6 and just apply some of the 
>>> changes from #34547? In particular, do things work if you don't include the 
>>> changes in all_cmdline.py?
>>>
>>> -- 
>>> John
>>>
>>>
>>> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:
>>>
 I just spent some time to debug this, but I failed.  The problem seems 
 to be that sage-shell:wait-for-redirection-to-complete in 
 https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
  
 does not return.  There is only one python file involved, 
 https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
  
 but I do not see what #34547 has to do with it.  Something about 
 lazy_import maybe?

 I can see that in sage-shell:run-cell-raw-output the command

 _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
  
 ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
 ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)

 was sent to the process (using process-send-string), and after that,

 (sage-shell:wait-for-redirection-to-complete)

 never returns.  I don't know how to debug the python code, 
 unfortunately.  Most importantly, I don't see what changed - what does 
 #34547 have to do with it?

 Martin



 On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:

> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems 
> that #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
> Not sure where to go from here.  Should I open a ticket on trac?
>
> For me personally, this is a blocker, but I have no idea how many 
> emacs users there are.
>
> Martin
>
>
> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>
>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  
>> I hope that all dependencies are in the branch.
>>
>> Martin
>>
>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>
>>> Could it be #34547, #16522, or #33842? I'm just taking guesses based 
>>> on the newly merged tickets.
>>>
>>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 
>>> emanuel.c...@gmail.com wrote:
>>>
 From someone called mantepse in the sage-shell-mode 
 
  issue 
 on github :

 ```
 It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 
 build. Apparently, if I first use the beta6 one for sage-shell-mode, I 
 can 
 then use beta7 in the same emacs session.
 ```

 I don't get it either...

 There are two short Python files in the current `sahe-shell-mode` 
 emacs package, which are my prime suspects for an incompatibility with 
 Python 3.11. Now for a strategy for debugging *this*...

 Any idea ?

 Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a 
 écrit :

> Emacs stopped working for me again!  I don't get it.
>

Re: [sage-release] Re: Sage 9.8.beta7 released

[Dima Pasechnik]

On Tue, Jan 24, 2023 at 10:15 PM John H Palmieri  wrote:
>
> For reasons I really don't understand, removing these lines from 
> sage.interfaces.all seem to have caused this:
>
> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
> -  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
> -  'mathematica', 'mwrank', 'octave', 'r', \
> -  'singular', 'sage0', 'sage']
>
> At least if I restore those lines, or even just add a line "interfaces = []", 
> then emacs appears to work again. I haven't tried it very much, though.

perhaps cause it's used in emacs_sage_shell.py ?

>
> I have absolutely no idea why this change would make a difference...
>
>
> On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de wrote:
>>
>> I tried to comment out all the changes in all_cmdline.py, but this didn't 
>> help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I 
>> don't see what could be a problem there.
>>
>> On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>>>
>>> This was one of my guesses because that ticket could have changed global 
>>> behavior of Sage by changing some imports — most of the tickets made more 
>>> focused changes. Can you start with 9.8.beta6 and just apply some of the 
>>> changes from #34547? In particular, do things work if you don't include the 
>>> changes in all_cmdline.py?
>>>
>>> --
>>> John
>>>
>>>
>>> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:

 I just spent some time to debug this, but I failed.  The problem seems to 
 be that sage-shell:wait-for-redirection-to-complete in 
 https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
  does not return.  There is only one python file involved, 
 https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
  but I do not see what #34547 has to do with it.  Something about 
 lazy_import maybe?

 I can see that in sage-shell:run-cell-raw-output the command

 _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
  ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
 ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)

 was sent to the process (using process-send-string), and after that,

 (sage-shell:wait-for-redirection-to-complete)

 never returns.  I don't know how to debug the python code, unfortunately.  
 Most importantly, I don't see what changed - what does #34547 have to do 
 with it?

 Martin



 On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>
> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
> Not sure where to go from here.  Should I open a ticket on trac?
>
> For me personally, this is a blocker, but I have no idea how many emacs 
> users there are.
>
> Martin
>
>
> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
>> hope that all dependencies are in the branch.
>>
>> Martin
>>
>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>>
>>> Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
>>> the newly merged tickets.
>>>
>>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
>>> wrote:

 From someone called mantepse in the sage-shell-mode issue on github :

 ```
 It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
 Apparently, if I first use the beta6 one for sage-shell-mode, I can 
 then use beta7 in the same emacs session.
 ```

 I don't get it either...

 There are two short Python files in the current `sahe-shell-mode` 
 emacs package, which are my prime suspects for an incompatibility with 
 Python 3.11. Now for a strategy for debugging *this*...

 Any idea ?

 Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>
> Emacs stopped working for me again!  I don't get it.
>
> This is terrible.
>
> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
> wrote:
>>
>> This patches fix my Fricas issue indeed. But losing the Emacs 
>> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>>
>> Thank you nevertheless !
>>
>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
>> écrit :
>>>
>>> In the hopes that this will fix it, I opened 

[sage-release] Re: Sage 9.8.beta7 released

[John H Palmieri]

For reasons I really don't understand, removing these lines from 
sage.interfaces.all seem to have caused this:

-interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
-  'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
-  'mathematica', 'mwrank', 'octave', 'r', \
-  'singular', 'sage0', 'sage']

At least if I restore those lines, or even just add a line "interfaces = 
[]", then emacs appears to work again. I haven't tried it very much, though.

I have absolutely no idea why this change would make a difference...


On Tuesday, January 24, 2023 at 12:52:29 PM UTC-8 axio...@yahoo.de wrote:

> I tried to comment out all the changes in all_cmdline.py, but this didn't 
> help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I 
> don't see what could be a problem there. 
>
> On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:
>
>> This was one of my guesses because that ticket could have changed global 
>> behavior of Sage by changing some imports — most of the tickets made more 
>> focused changes. Can you start with 9.8.beta6 and just apply some of the 
>> changes from #34547? In particular, do things work if you don't include the 
>> changes in all_cmdline.py?
>>
>> -- 
>> John
>>
>>
>> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:
>>
>>> I just spent some time to debug this, but I failed.  The problem seems 
>>> to be that sage-shell:wait-for-redirection-to-complete in 
>>> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>>>  
>>> does not return.  There is only one python file involved, 
>>> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py,
>>>  
>>> but I do not see what #34547 has to do with it.  Something about 
>>> lazy_import maybe?
>>>
>>> I can see that in sage-shell:run-cell-raw-output the command
>>>
>>> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>>>  
>>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
>>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>>>
>>> was sent to the process (using process-send-string), and after that,
>>>
>>> (sage-shell:wait-for-redirection-to-complete)
>>>
>>> never returns.  I don't know how to debug the python code, 
>>> unfortunately.  Most importantly, I don't see what changed - what does 
>>> #34547 have to do with it?
>>>
>>> Martin
>>>
>>>
>>>
>>> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>>>
 Indeed, that was a great suggestion: 9.8.beta6 works - and it seems 
 that #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
 Not sure where to go from here.  Should I open a ticket on trac?

 For me personally, this is a blocker, but I have no idea how many emacs 
 users there are.

 Martin


 On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:

> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
> hope that all dependencies are in the branch.
>
> Martin
>
> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>
>> Could it be #34547, #16522, or #33842? I'm just taking guesses based 
>> on the newly merged tickets.
>>
>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 
>> emanuel.c...@gmail.com wrote:
>>
>>> From someone called mantepse in the sage-shell-mode 
>>> 
>>>  issue 
>>> on github :
>>>
>>> ```
>>> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 
>>> build. Apparently, if I first use the beta6 one for sage-shell-mode, I 
>>> can 
>>> then use beta7 in the same emacs session.
>>> ```
>>>
>>> I don't get it either...
>>>
>>> There are two short Python files in the current `sahe-shell-mode` 
>>> emacs package, which are my prime suspects for an incompatibility with 
>>> Python 3.11. Now for a strategy for debugging *this*...
>>>
>>> Any idea ?
>>>
>>> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a 
>>> écrit :
>>>
 Emacs stopped working for me again!  I don't get it.

 This is terrible.

 On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
 wrote:

> This patches fix my Fricas issue indeed. But losing the Emacs 
> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>
> Thank you nevertheless !
>
> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
> écrit :
>
>> In the hopes that this will fix it, I opened 
>> https://trac.sagemath.org/ticket/34927.
>>
>>
>>
>> On Friday, 

Re: [sage-release] Re: Sage 9.8.beta7 released

[simplyelliptic]

On my Mac OS13.* with updated homebrew,and Intel Core i5,it compiled from the first build and make ptestlong all passed…. Kenji 23/01/2023 21:32、John H Palmieri のメール:Could it be #34547, #16522, or #33842? I'm just taking guesses based on the newly merged tickets.On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com wrote:From someone called mantepse in the sage-shell-mode issue on github :```It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. Apparently, if I first use the beta6 one for sage-shell-mode, I can then use beta7 in the same emacs session.```I don't get it either...There are two short Python files in the current `sahe-shell-mode` emacs package, which are my prime suspects for an incompatibility with Python 3.11. Now for a strategy for debugging *this*...Any idea ?Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :Emacs stopped working for me again!  I don't get it.This is terrible.On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com wrote:This patches fix my Fricas issue indeed. But losing the Emacs interface is a big hit for me, so I revert to 9.6.beta6 for now.Thank you nevertheless !Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :In the hopes that this will fix it, I opened https://trac.sagemath.org/ticket/34927.On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:Does this change fix the fricas.py failure?diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.pyindex dc2ce71f26..ceba6f90dc 100644--- a/src/sage/interfaces/fricas.py+++ b/src/sage/interfaces/fricas.py@@ -891,7 +891,7 @@ http://fricas.sourceforge.net.         """         EXAMPLES:: -            sage: fricas.__reduce__()                                           # optional - fricas+            sage: FriCAS().__reduce__()                                         # optional - fricas             (, ())             sage: f, args = _                                                   # optional - fricas             sage: f(*args) On Friday, January 20, 2023 at 12:34:21 PM UTC-8 emanuel.c...@gmail.com wrote:Apart from the  Emacs issye alteady reported, I get the three permanent failures I reported for the previous betas, as well as a new one, which gives three errors :charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 src/sage/interfaces/fricas.py  # 3 doctests failedRunning doctests with ID 2023-01-20-20-50-00-ee865d6d.Git branch: developGit ref: 9.8.beta7Running with SAGE_LOCAL='/usr/local/sage-9/local' and SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'Using --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkgFeatures to be detected: 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlibDoctesting 1 file.sage -t --long --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 src/sage/interfaces/fricas.py**File "src/sage/interfaces/fricas.py", line 894, in sage.interfaces.fricas.FriCAS.__reduce__Failed example:    fricas.__reduce__()                                           # optional - fricasException raised:    Traceback (most recent call last):      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run        self.compile_and_execute(example, compiler, test.globs)      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in compile_and_execute        exec(compiled, globs)      File "", line 1, in         fricas.__reduce__()                                           # optional - fricas      File "/usr/lib/python3.10/copyreg.py", line 76, in _reduce_ex        raise TypeError(f"cannot pickle {cls.__name__!r} object")    TypeError: cannot pickle 'LazyImport' object**File "src/sage/interfaces/fricas.py", line 896, in sage.interfaces.fricas.FriCAS.__reduce__Failed example:    f, args = _                                                   # optional - fricasException raised:    Traceback (most recent call last):      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run        self.compile_and_execute(example, compiler, test.globs)      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in 

[sage-release] Re: Sage 9.8.beta7 released

['axio...@yahoo.de' via sage-release]

I tried to comment out all the changes in all_cmdline.py, but this didn't 
help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I 
don't see what could be a problem there. 

On Tuesday, 24 January 2023 at 17:47:29 UTC+1 John H Palmieri wrote:

> This was one of my guesses because that ticket could have changed global 
> behavior of Sage by changing some imports — most of the tickets made more 
> focused changes. Can you start with 9.8.beta6 and just apply some of the 
> changes from #34547? In particular, do things work if you don't include the 
> changes in all_cmdline.py?
>
> -- 
> John
>
>
> On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:
>
>> I just spent some time to debug this, but I failed.  The problem seems to 
>> be that sage-shell:wait-for-redirection-to-complete in 
>> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>>  
>> does not return.  There is only one python file involved, 
>> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py, 
>> but I do not see what #34547 has to do with it.  Something about 
>> lazy_import maybe?
>>
>> I can see that in sage-shell:run-cell-raw-output the command
>>
>> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>>  
>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
>> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>>
>> was sent to the process (using process-send-string), and after that,
>>
>> (sage-shell:wait-for-redirection-to-complete)
>>
>> never returns.  I don't know how to debug the python code, 
>> unfortunately.  Most importantly, I don't see what changed - what does 
>> #34547 have to do with it?
>>
>> Martin
>>
>>
>>
>> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>>
>>> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
>>> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
>>> Not sure where to go from here.  Should I open a ticket on trac?
>>>
>>> For me personally, this is a blocker, but I have no idea how many emacs 
>>> users there are.
>>>
>>> Martin
>>>
>>>
>>> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>>
 Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
 hope that all dependencies are in the branch.

 Martin

 On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:

> Could it be #34547, #16522, or #33842? I'm just taking guesses based 
> on the newly merged tickets.
>
> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 
> emanuel.c...@gmail.com wrote:
>
>> From someone called mantepse in the sage-shell-mode 
>> 
>>  issue 
>> on github :
>>
>> ```
>> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
>> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
>> use beta7 in the same emacs session.
>> ```
>>
>> I don't get it either...
>>
>> There are two short Python files in the current `sahe-shell-mode` 
>> emacs package, which are my prime suspects for an incompatibility with 
>> Python 3.11. Now for a strategy for debugging *this*...
>>
>> Any idea ?
>>
>> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>>
>>> Emacs stopped working for me again!  I don't get it.
>>>
>>> This is terrible.
>>>
>>> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
>>> wrote:
>>>
 This patches fix my Fricas issue indeed. But losing the Emacs 
 interface is a big hit for me, so I revert to 9.6.beta6 for now.

 Thank you nevertheless !

 Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
 écrit :

> In the hopes that this will fix it, I opened 
> https://trac.sagemath.org/ticket/34927.
>
>
>
> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri 
> wrote:
>
>> Does this change fix the fricas.py failure?
>>
>> diff --git a/src/sage/interfaces/fricas.py 
>> b/src/sage/interfaces/fricas.py
>> index dc2ce71f26..ceba6f90dc 100644
>> --- a/src/sage/interfaces/fricas.py
>> +++ b/src/sage/interfaces/fricas.py
>> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>>  """
>>  EXAMPLES::
>>  
>> -sage: fricas.__reduce__()   
>> # optional - fricas
>> +sage: FriCAS().__reduce__() 
>> # optional - fricas
>>  (, ())

[sage-release] Re: Sage 9.8 Release Tour

[Matthias Köppe]

So far we have:


   1. 
  1. Linear algebra 
  
 1. Submodules of tensor modules with prescribed symmetries 
 

 2. Free module isomorphisms corresponding to fixed standard bases 
 of … 
 

  2. Commutative algebra 
  
 1. Solving polynomial systems using msolve 
 

 2. Lazy power series ring 
 

 3. Miscellaneous 
 
  3. Algebra 
  
  4. Polyhedral geometry 
  
  5. Number theory 
  
  6. New packages and package upgrades 
  

 1. SCIP Optimization Suite 8.0 
 

 2. msolve: polynomial system solver 
 

 3. Kissat SAT Solver 
 
 4. Python 3.11 
 
 5. Other package upgrades 
 

  7. New tools for developers 
  

 1. tox -e docker-...-incremental 
 

 2. ./configure --enable-wheels 
 

 3. make -j list-broken-packages 
 

  8. Configuration changes 
  

 1. Support for GCC < 8 dropped; C++17 features now available 
 

 2. Native support for Apple Silicon (M1/M2) 
 

  9. Availability of Sage 9.8 and installation help 
  

 1. Sources 
 
  10. More details 
  
   

On Wednesday, January 18, 2023 at 5:13:42 PM UTC-8 Kwankyu Lee wrote:

> It's time to work on the release tour for the upcoming 9.8 release 
> https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/f8f81157-1a80-4749-8855-17788a62e429n%40googlegroups.com.

[sage-release] Re: Sage 9.8.beta7 released

[John H Palmieri]

This was one of my guesses because that ticket could have changed global 
behavior of Sage by changing some imports — most of the tickets made more 
focused changes. Can you start with 9.8.beta6 and just apply some of the 
changes from #34547? In particular, do things work if you don't include the 
changes in all_cmdline.py?

-- 
John


On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:

> I just spent some time to debug this, but I failed.  The problem seems to 
> be that sage-shell:wait-for-redirection-to-complete in 
> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>  
> does not return.  There is only one python file involved, 
> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py, 
> but I do not see what #34547 has to do with it.  Something about 
> lazy_import maybe?
>
> I can see that in sage-shell:run-cell-raw-output the command
>
> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>  
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>
> was sent to the process (using process-send-string), and after that,
>
> (sage-shell:wait-for-redirection-to-complete)
>
> never returns.  I don't know how to debug the python code, unfortunately.  
> Most importantly, I don't see what changed - what does #34547 have to do 
> with it?
>
> Martin
>
>
>
> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>
>> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
>> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
>> Not sure where to go from here.  Should I open a ticket on trac?
>>
>> For me personally, this is a blocker, but I have no idea how many emacs 
>> users there are.
>>
>> Martin
>>
>>
>> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
>>> hope that all dependencies are in the branch.
>>>
>>> Martin
>>>
>>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>>
 Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
 the newly merged tickets.

 On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
 wrote:

> From someone called mantepse in the sage-shell-mode 
> 
>  issue 
> on github :
>
> ```
> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
> use beta7 in the same emacs session.
> ```
>
> I don't get it either...
>
> There are two short Python files in the current `sahe-shell-mode` 
> emacs package, which are my prime suspects for an incompatibility with 
> Python 3.11. Now for a strategy for debugging *this*...
>
> Any idea ?
>
> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>
>> Emacs stopped working for me again!  I don't get it.
>>
>> This is terrible.
>>
>> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
>> wrote:
>>
>>> This patches fix my Fricas issue indeed. But losing the Emacs 
>>> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>>>
>>> Thank you nevertheless !
>>>
>>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
>>> écrit :
>>>
 In the hopes that this will fix it, I opened 
 https://trac.sagemath.org/ticket/34927.



 On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri 
 wrote:

> Does this change fix the fricas.py failure?
>
> diff --git a/src/sage/interfaces/fricas.py 
> b/src/sage/interfaces/fricas.py
> index dc2ce71f26..ceba6f90dc 100644
> --- a/src/sage/interfaces/fricas.py
> +++ b/src/sage/interfaces/fricas.py
> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>  """
>  EXAMPLES::
>  
> -sage: fricas.__reduce__() 
>   # optional - fricas
> +sage: FriCAS().__reduce__()   
>   # optional - fricas
>  (, ())
>  sage: f, args = _ 
>   # optional - fricas
>  sage: f(*args) 
>
>
>
> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
> emanuel.c...@gmail.com wrote:
>
>> Apart from the  Emacs issye alteady reported 
>> 

[sage-release] Re: Sage 9.8.beta7 released

[Matthias Köppe]

>From looking at that file:
https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py#L159

In 9.8.beta7:

sage: isinstance(axiom, sage.interfaces.expect.Expect)
False

On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:

> I just spent some time to debug this, but I failed.  The problem seems to 
> be that sage-shell:wait-for-redirection-to-complete in 
> https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
>  
> does not return.  There is only one python file involved, 
> https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py, 
> but I do not see what #34547 has to do with it.  Something about 
> lazy_import maybe?
>
> I can see that in sage-shell:run-cell-raw-output the command
>
> _emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
>  
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
> ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)
>
> was sent to the process (using process-send-string), and after that,
>
> (sage-shell:wait-for-redirection-to-complete)
>
> never returns.  I don't know how to debug the python code, unfortunately.  
> Most importantly, I don't see what changed - what does #34547 have to do 
> with it?
>
> Martin
>
>
>
> On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:
>
>> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
>> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
>> Not sure where to go from here.  Should I open a ticket on trac?
>>
>> For me personally, this is a blocker, but I have no idea how many emacs 
>> users there are.
>>
>> Martin
>>
>>
>> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>>
>>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
>>> hope that all dependencies are in the branch.
>>>
>>> Martin
>>>
>>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>>
 Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
 the newly merged tickets.

 On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
 wrote:

> From someone called mantepse in the sage-shell-mode 
> 
>  issue 
> on github :
>
> ```
> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
> use beta7 in the same emacs session.
> ```
>
> I don't get it either...
>
> There are two short Python files in the current `sahe-shell-mode` 
> emacs package, which are my prime suspects for an incompatibility with 
> Python 3.11. Now for a strategy for debugging *this*...
>
> Any idea ?
>
> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>
>> Emacs stopped working for me again!  I don't get it.
>>
>> This is terrible.
>>
>> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
>> wrote:
>>
>>> This patches fix my Fricas issue indeed. But losing the Emacs 
>>> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>>>
>>> Thank you nevertheless !
>>>
>>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
>>> écrit :
>>>
 In the hopes that this will fix it, I opened 
 https://trac.sagemath.org/ticket/34927.



 On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri 
 wrote:

> Does this change fix the fricas.py failure?
>
> diff --git a/src/sage/interfaces/fricas.py 
> b/src/sage/interfaces/fricas.py
> index dc2ce71f26..ceba6f90dc 100644
> --- a/src/sage/interfaces/fricas.py
> +++ b/src/sage/interfaces/fricas.py
> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>  """
>  EXAMPLES::
>  
> -sage: fricas.__reduce__() 
>   # optional - fricas
> +sage: FriCAS().__reduce__()   
>   # optional - fricas
>  (, ())
>  sage: f, args = _ 
>   # optional - fricas
>  sage: f(*args) 
>
>
>
> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
> emanuel.c...@gmail.com wrote:
>
>> Apart from the  Emacs issye alteady reported 
>> ,
>>  
>> I get the three permanent failures I reported for the previous 
>> betas, as 

[sage-release] Re: Sage 9.8.beta7 released

['axio...@yahoo.de' via sage-release]

I just spent some time to debug this, but I failed.  The problem seems to 
be that sage-shell:wait-for-redirection-to-complete in 
https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889
 
does not return.  There is only one python file involved, 
https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py, 
but I do not see what #34547 has to do with it.  Something about 
lazy_import maybe?

I can see that in sage-shell:run-cell-raw-output the command

_emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()",
 
’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, 
’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)

was sent to the process (using process-send-string), and after that,

(sage-shell:wait-for-redirection-to-complete)

never returns.  I don't know how to debug the python code, unfortunately.  
Most importantly, I don't see what changed - what does #34547 have to do 
with it?

Martin



On Tuesday, 24 January 2023 at 11:09:23 UTC+1 axio...@yahoo.de wrote:

> Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
> #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
> Not sure where to go from here.  Should I open a ticket on trac?
>
> For me personally, this is a blocker, but I have no idea how many emacs 
> users there are.
>
> Martin
>
>
> On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:
>
>> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
>> hope that all dependencies are in the branch.
>>
>> Martin
>>
>> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>>
>>> Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
>>> the newly merged tickets.
>>>
>>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
>>> wrote:
>>>
 From someone called mantepse in the sage-shell-mode 
 
  issue 
 on github :

 ```
 It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
 Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
 use beta7 in the same emacs session.
 ```

 I don't get it either...

 There are two short Python files in the current `sahe-shell-mode` emacs 
 package, which are my prime suspects for an incompatibility with Python 
 3.11. Now for a strategy for debugging *this*...

 Any idea ?

 Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :

> Emacs stopped working for me again!  I don't get it.
>
> This is terrible.
>
> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
> wrote:
>
>> This patches fix my Fricas issue indeed. But losing the Emacs 
>> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>>
>> Thank you nevertheless !
>>
>> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a 
>> écrit :
>>
>>> In the hopes that this will fix it, I opened 
>>> https://trac.sagemath.org/ticket/34927.
>>>
>>>
>>>
>>> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri 
>>> wrote:
>>>
 Does this change fix the fricas.py failure?

 diff --git a/src/sage/interfaces/fricas.py 
 b/src/sage/interfaces/fricas.py
 index dc2ce71f26..ceba6f90dc 100644
 --- a/src/sage/interfaces/fricas.py
 +++ b/src/sage/interfaces/fricas.py
 @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
  """
  EXAMPLES::
  
 -sage: fricas.__reduce__() 
   # optional - fricas
 +sage: FriCAS().__reduce__()   
   # optional - fricas
  (, ())
  sage: f, args = _ 
   # optional - fricas
  sage: f(*args) 



 On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
 emanuel.c...@gmail.com wrote:

> Apart from the  Emacs issye alteady reported 
> ,
>  
> I get the three permanent failures I reported for the previous betas, 
> as 
> well as a new one, which gives three errors :
>
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long 
> --warn-long 259.6 
> --random-seed=41414648133166628206443904124754495105 
> src/sage/interfaces/fricas.py  # 3 doctests failed
> Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
> Git branch: develop
> Git ref: 

[sage-release] Re: Sage 9.8.beta7 released

['axio...@yahoo.de' via sage-release]

Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that 
#16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
Not sure where to go from here.  Should I open a ticket on trac?

For me personally, this is a blocker, but I have no idea how many emacs 
users there are.

Martin


On Tuesday, 24 January 2023 at 10:21:11 UTC+1 axio...@yahoo.de wrote:

> Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I 
> hope that all dependencies are in the branch.
>
> Martin
>
> On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:
>
>> Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
>> the newly merged tickets.
>>
>> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
>> wrote:
>>
>>> From someone called mantepse in the sage-shell-mode 
>>> 
>>>  issue 
>>> on github :
>>>
>>> ```
>>> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
>>> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
>>> use beta7 in the same emacs session.
>>> ```
>>>
>>> I don't get it either...
>>>
>>> There are two short Python files in the current `sahe-shell-mode` emacs 
>>> package, which are my prime suspects for an incompatibility with Python 
>>> 3.11. Now for a strategy for debugging *this*...
>>>
>>> Any idea ?
>>>
>>> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>>>
 Emacs stopped working for me again!  I don't get it.

 This is terrible.

 On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
 wrote:

> This patches fix my Fricas issue indeed. But losing the Emacs 
> interface is a big hit for me, so I revert to 9.6.beta6 for now.
>
> Thank you nevertheless !
>
> Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :
>
>> In the hopes that this will fix it, I opened 
>> https://trac.sagemath.org/ticket/34927.
>>
>>
>>
>> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
>>
>>> Does this change fix the fricas.py failure?
>>>
>>> diff --git a/src/sage/interfaces/fricas.py 
>>> b/src/sage/interfaces/fricas.py
>>> index dc2ce71f26..ceba6f90dc 100644
>>> --- a/src/sage/interfaces/fricas.py
>>> +++ b/src/sage/interfaces/fricas.py
>>> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>>>  """
>>>  EXAMPLES::
>>>  
>>> -sage: fricas.__reduce__()   
>>> # optional - fricas
>>> +sage: FriCAS().__reduce__() 
>>> # optional - fricas
>>>  (, ())
>>>  sage: f, args = _   
>>> # optional - fricas
>>>  sage: f(*args) 
>>>
>>>
>>>
>>> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
>>> emanuel.c...@gmail.com wrote:
>>>
 Apart from the  Emacs issye alteady reported 
 ,
  
 I get the three permanent failures I reported for the previous betas, 
 as 
 well as a new one, which gives three errors :

 charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long 
 --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 
 src/sage/interfaces/fricas.py  # 3 doctests failed
 Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
 Git branch: develop
 Git ref: 9.8.beta7
 Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
 SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
 Using 
 --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
 Features to be detected: 
 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
 Doctesting 1 file.
 sage -t --long --warn-long 259.6 
 --random-seed=41414648133166628206443904124754495105 
 src/sage/interfaces/fricas.py

 **
 File 

[sage-release] Re: Sage 9.8.beta7 released

['axio...@yahoo.de' via sage-release]

Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I hope 
that all dependencies are in the branch.

Martin

On Monday, 23 January 2023 at 21:32:10 UTC+1 John H Palmieri wrote:

> Could it be #34547, #16522, or #33842? I'm just taking guesses based on 
> the newly merged tickets.
>
> On Monday, January 23, 2023 at 10:42:37 AM UTC-8 emanuel.c...@gmail.com 
> wrote:
>
>> From someone called mantepse in the sage-shell-mode 
>> 
>>  issue 
>> on github :
>>
>> ```
>> It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. 
>> Apparently, if I first use the beta6 one for sage-shell-mode, I can then 
>> use beta7 in the same emacs session.
>> ```
>>
>> I don't get it either...
>>
>> There are two short Python files in the current `sahe-shell-mode` emacs 
>> package, which are my prime suspects for an incompatibility with Python 
>> 3.11. Now for a strategy for debugging *this*...
>>
>> Any idea ?
>>
>> Le lundi 23 janvier 2023 à 10:48:48 UTC+1, axio...@yahoo.de a écrit :
>>
>>> Emacs stopped working for me again!  I don't get it.
>>>
>>> This is terrible.
>>>
>>> On Sunday, 22 January 2023 at 14:41:04 UTC+1 emanuel.c...@gmail.com 
>>> wrote:
>>>
 This patches fix my Fricas issue indeed. But losing the Emacs interface 
 is a big hit for me, so I revert to 9.6.beta6 for now.

 Thank you nevertheless !

 Le vendredi 20 janvier 2023 à 22:58:53 UTC+1, John H Palmieri a écrit :

> In the hopes that this will fix it, I opened 
> https://trac.sagemath.org/ticket/34927.
>
>
>
> On Friday, January 20, 2023 at 1:46:02 PM UTC-8 John H Palmieri wrote:
>
>> Does this change fix the fricas.py failure?
>>
>> diff --git a/src/sage/interfaces/fricas.py 
>> b/src/sage/interfaces/fricas.py
>> index dc2ce71f26..ceba6f90dc 100644
>> --- a/src/sage/interfaces/fricas.py
>> +++ b/src/sage/interfaces/fricas.py
>> @@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
>>  """
>>  EXAMPLES::
>>  
>> -sage: fricas.__reduce__()   
>> # optional - fricas
>> +sage: FriCAS().__reduce__() 
>> # optional - fricas
>>  (, ())
>>  sage: f, args = _   
>> # optional - fricas
>>  sage: f(*args) 
>>
>>
>>
>> On Friday, January 20, 2023 at 12:34:21 PM UTC-8 
>> emanuel.c...@gmail.com wrote:
>>
>>> Apart from the  Emacs issye alteady reported 
>>> ,
>>>  
>>> I get the three permanent failures I reported for the previous betas, 
>>> as 
>>> well as a new one, which gives three errors :
>>>
>>> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 
>>> 259.6 --random-seed=41414648133166628206443904124754495105 
>>> src/sage/interfaces/fricas.py  # 3 doctests failed
>>> Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
>>> Git branch: develop
>>> Git ref: 9.8.beta7
>>> Running with SAGE_LOCAL='/usr/local/sage-9/local' and 
>>> SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
>>> Using 
>>> --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
>>> Features to be detected: 
>>> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
>>> Doctesting 1 file.
>>> sage -t --long --warn-long 259.6 
>>> --random-seed=41414648133166628206443904124754495105 
>>> src/sage/interfaces/fricas.py
>>>
>>> **
>>> File "src/sage/interfaces/fricas.py", line 894, in 
>>> sage.interfaces.fricas.FriCAS.__reduce__
>>> Failed example:
>>> fricas.__reduce__()   # 
>>> optional - fricas
>>> Exception raised:
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, 
>>> in _run
>>> self.compile_and_execute(example, compiler, test.globs)
>>>   File