[sage-devel] Re: scipy failed in sage-8.1

Mon 2018-03-19 21:30:59 UTC: > > On a separate issue, I find it sad to have to use Google to contact Sage. The questions and answers site "Ask Sage" at https://ask.sagemath.org/ lets you ask questions in a different environment. -- You received this message because you are subscribed to the

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

Related ticket, mentioning var and automatic_names: - SageMath #9048: inconsistencies between the terminal version and the notebook https://trac.sagemath.org/ticket/9048 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] scipy failed in sage-8.1

Was it an upgrade from a previous version of sage? > On 20/03/2018, at 10:29, malc1519 via sage-devel > wrote: > > I was trying to build Sage 8.1 on a Dell Inspiron 5000 2-in-1, with i7 > processor, > running Scientific Linux 7.x. I got the following > >

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

On Mon, Mar 19, 2018 at 12:43 PM, Thierry wrote: > On Mon, Mar 19, 2018 at 08:32:23AM -0700, Nils Bruin wrote: >> On Monday, March 19, 2018 at 8:04:07 AM UTC-7, Emmanuel Charpentier wrote: >> > >> > >> > >> >- Some functions (mostly inherited from Maxima) *do*

Re: [sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

On Mon, Mar 19, 2018 at 4:42 AM, Erik Bray wrote: > It looks like, just from reading the Jupyter docs, this where we can > control what '?' returns at the kernel level: > http://jupyter-client.readthedocs.io/en/stable/messaging.html#introspection > > So if Sage could just

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

On Mon, Mar 19, 2018 at 08:32:23AM -0700, Nils Bruin wrote: > On Monday, March 19, 2018 at 8:04:07 AM UTC-7, Emmanuel Charpentier wrote: > > > > > > > >- Some functions (mostly inherited from Maxima) *do* already create > >new symbolic variables, but do not inject them in the relevant >

[sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

Hi, Another issue involving the Jupyter notebook and LaTeX is that typeset outputs, which are correctly rendered with MathJax in the browser, are no longer typeset when exporting the notebook to pdf: https://trac.sagemath.org/ticket/23330 Probably the two issues are not related (or maybe they

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

On Monday, March 19, 2018 at 8:04:07 AM UTC-7, Emmanuel Charpentier wrote: > > > >- Some functions (mostly inherited from Maxima) *do* already create >new symbolic variables, but do not inject them in the relevant namespace. >In *this* case (and this case only), I'd like to have this

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

Addendum to the previous answer : solve at least may generate symbolic constants with domain constraints. If we accept the idea of auto-declaring them, should we add the relevant constraints ? Example : sage: var("x,y") (x, y) sage: solve([3*x+y==0,6*x==-2*y],[x,y]) [[x == -1/3*r1, y == r1]]

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

To summarize the previous answers (and nitpick a bit) : automatic_names - may come handy ; - shouldn't be mandatory - shouldn't be the default - should print a warning when fired. I also liked the idea of introducing a new magic controlling that feature. However, I have a couple

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

On 19/03/18 15:06, Nicolas M. Thiery wrote: On Thu, Mar 15, 2018 at 08:49:02AM -0700, William Stein wrote: On Thu, Mar 15, 2018 at 7:43 AM, Emmanuel Charpentier wrote: [...] However, most CASes now available do away without this mandatory declaration. And

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

On Thu, Mar 15, 2018 at 08:49:02AM -0700, William Stein wrote: > 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

Re: [sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

On Monday, March 19, 2018 at 11:52:55 AM UTC, Erik Bray wrote: > > On Mon, Mar 19, 2018 at 12:16 PM, Emmanuel Charpentier > wrote: > > > > > > Le lundi 19 mars 2018 11:44:33 UTC+1, Erik Bray a écrit : > >> > >> This question raised an issue I was not aware of (and

Re: [sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

On Mon, Mar 19, 2018 at 12:36 PM, Erik Bray wrote: > On Mon, Mar 19, 2018 at 12:16 PM, Emmanuel Charpentier > wrote: >> >> >> Le lundi 19 mars 2018 11:44:33 UTC+1, Erik Bray a écrit : >>> >>> This question raised an issue I was not aware of

Re: [sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

On Mon, Mar 19, 2018 at 12:16 PM, Emmanuel Charpentier wrote: > > > Le lundi 19 mars 2018 11:44:33 UTC+1, Erik Bray a écrit : >> >> This question raised an issue I was not aware of (and didn't see any >> existing tickets for): >> >>

[sage-devel] Re: Shortcoming in Jupyter Notebook w.r.t. latex in help

Le lundi 19 mars 2018 11:44:33 UTC+1, Erik Bray a écrit : > > This question raised an issue I was not aware of (and didn't see any > existing tickets for): > > https://ask.sagemath.org/question/41592/inside-help-not-processed/# > > When viewing docs for Sage objects in the Jupyter Notebook,

[sage-devel] Shortcoming in Jupyter Notebook w.r.t. latex in help

This question raised an issue I was not aware of (and didn't see any existing tickets for): https://ask.sagemath.org/question/41592/inside-help-not-processed/# When viewing docs for Sage objects in the Jupyter Notebook, they are just displayed as plain text--this is a major shortcoming over