Re: [sage-devel] Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread Sébastien Labbé
On Tuesday, March 13, 2018 at 11:32:15 PM UTC+1, Travis Scrimshaw wrote: > > > > On Wednesday, March 14, 2018 at 3:39:14 AM UTC+10, vdelecroix wrote: >> >> I remember somebdy implementing directly in Ipython at some Sage days >> (there is a way to plug hooks as we do with the preparser). The hoo

[sage-devel] Re: Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread Simon King
On 2018-03-15, William Stein wrote: > I don't remember, but automatic_names can (or should) print a message > when it automatically creates a new symbolic variable -- this helps > deal with some people's concerns... Indeed. Having a warning message alerting the user of potentially unintended beha

Re: [sage-devel] Re: Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread William Stein
On Thu, Mar 15, 2018 at 7:43 AM, Emmanuel Charpentier wrote: > [...] However, most CASes now available do away without this mandatory > declaration. And hence Sage should have automatic_names as a non-default *option*. See the mission statement, which is to create a viable alternative to Maple,

[sage-devel] Re: Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread Simon King
Hi Emmanuel, On 2018-03-15, Emmanuel Charpentier wrote: > One has also to consider the case (important in Sage) of the > indeterminate(s) of a polynomial. Do we risk introducing an ambiguity if > allowing automatic variable declaration ? Of course. If you create a polynomial ring (explicitly o

[sage-devel] Re: Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread Emmanuel Charpentier
Such a feature might come in handy so solve a couple of cases where sage creates (or receives from its subsystems) a symbolic expression with "new" variables. Two chronic offenders are Maxima's solver and differential equation solver(s), which routinely add new symbolic constants as required by

Re: [sage-devel] Re: Move the automatic_names() feature into the Sage interpreter proper

2018-03-15 Thread kcrisman
> > Anyway, certainly it should (in principle) be *implemented* for any Sage > > interface, including Jupyter. I just don't know about it becoming the > > default. > > Certainly nobody's talking about turning it on by default--just that > the feature exists, people do use it, and there's no

[sage-devel] Re: Block TermOrder equality is broken

2018-03-15 Thread Simon King
On 2018-03-15, Simon King wrote: >sage: R = PolynomialRing(QQ, 6, 'x', order="lex(1),degrevlex(5)") >sage: S = R.change_ring(order="lex(2),degrevlex(4)") >sage: R is S >True > > So, indeed it is a bug. ... which is being dealt with at https://trac.sagemath.org/ticket/24981 Kind r