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

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

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

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

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

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

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

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',

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

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',

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

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

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

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

[sage-release] Re: Sage 9.8 Release Tour

So far we have: 1. 1. Linear algebra 1. Submodules of tensor modules with prescribed symmetries

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

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

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

>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

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

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

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

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.

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

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.