[sage-devel] Re: Piecewise functions in Sage 7.2

Automatic creation of a symbolic function from a numeric one sounds like a good idea to me, if feasible. I'm coming to Sage from Mathematica, where one doesn't need to think about such issues. It's confusing to new users when numeric functions fail unexpectedly. On Sunday, May 22, 2016 at

[sage-devel] Why do we discard (repeatedly) all warning filters?

At the moment any time a deprecation warning is issued all warning filters are thrown away: https://github.com/sagemath/sage/blob/master/src/sage/misc/superseded.py#L138 which means that Python functionality for tuning warnings is completely useless. Why??? If the point is to change the default

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

On Sunday, 22 May 2016 15:27:26 UTC-6, paulmasson wrote: > > Still getting the problem. Occurs on about half of page loads right now. > Here's a link to an index page for the repository: > > http://paulmasson.github.io/sagemath-docs/functions.html > > The interacts are on pages for anything

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

Still getting the problem. Occurs on about half of page loads right now. Here's a link to an index page for the repository: http://paulmasson.github.io/sagemath-docs/functions.html The interacts are on pages for anything with an index, so try the Bessel or elliptic functions. Not all of the

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

On Sunday, 22 May 2016 14:01:26 UTC-6, paulmasson wrote: > > Andrey, I have a bunch of simple interacts in Github pages of this sort > > @interact > > def _( n=slider(0,10,step_size=1) ): > > show( plot( bessel_J(n,x), x, 0, n+20, figsize=[4,2], color=(0,.5,1) ) ) > > > that randomly fail to

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

Not a bug in Sage 7.2, just lots of new behavior for piecewise. On Tuesday, May 17, 2016 at 2:42:06 PM UTC-7, paulmasson wrote: > > Andrey, I've confirmed that the error comes from the piecewise function > and not the interacts. Looks like a bug in Sage 7.2, not in the test server. > > On

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

Andrey, I have a bunch of simple interacts in Github pages of this sort @interact def _( n=slider(0,10,step_size=1) ): show( plot( bessel_J(n,x), x, 0, n+20, figsize=[4,2], color=(0,.5,1) ) ) that randomly fail to interact. The server returns an initial image but the interact doesn't

Re: [sage-devel] Re: weird output: show of FiniteField

On Sun, May 22, 2016 at 3:16 AM, Volker Braun wrote: > PS: I'd be more than happy to get rid of the special casing for > pretty_print, there is no reason to list iterators beyond backward > compatibility for a pretty weird use case. +1. There are many changes that should

[sage-devel] Re: Problem with string.py and math.py

"." is in sys.path unless others have write permissions on the current directory. On Sunday, May 22, 2016 at 3:55:23 PM UTC+2, Jeroen Sijsling wrote: > > Dear all, > > (I also posted this about a quarter of an hour ago, but I now think that I > must have done something wrong. I am sorry if

[sage-devel] Problem with string.py and math.py

Dear all, (I also posted this about a quarter of an hour ago, but I now think that I must have done something wrong. I am sorry if this turns out to be a double post.) For some reason I placed a file called string.py in the directory where I normally run Sage. I then ran Sage in the usual

[sage-devel] Re: weird output: show of FiniteField

PS: I'd be more than happy to get rid of the special casing for pretty_print, there is no reason to list iterators beyond backward compatibility for a pretty weird use case. On Sunday, May 22, 2016 at 12:05:10 PM UTC+2, Volker Braun wrote: > > For historic reasons, pretty_print() of iterators

[sage-devel] Re: weird output: show of FiniteField

For historic reasons, pretty_print() of iterators lists elements: sage: pretty_print(iter([1,2,3])) 1 2 3 And finite fields are iterators: sage: isinstance(GF(2), collections.Iterator) True On Sunday, May 22, 2016 at 11:47:50 AM UTC+2, Daniel Krenn wrote: > > We have > > sage:

[sage-devel] weird output: show of FiniteField

We have sage: show(FiniteField(2)) \newcommand{\Bold}[1]{\mathbf{#1}}0 1 which is the list of elements and not $F_2$ (what I would expect). However, the LaTeX-representation is fine: sage: latex(FiniteField(2)) \Bold{F}_{2} Note that on SMC show behaves differently and a typeset

[sage-devel] Re: Piecewise functions in Sage 7.2

sage: g(x,u) = integral(u^2,u,0,x) sage: f=piecewise([ [(0,1), g(x,u) ] ]) sage: f piecewise(x|-->1/3*x^3 on (0, 1); x) On Sunday, May 22, 2016 at 10:14:13 AM UTC+2, Volker Braun wrote: > > Piecewise functions are symbolic functions now; The problem is that your g > doesn't define a symbolic

[sage-devel] Re: Piecewise functions in Sage 7.2

Piecewise functions are symbolic functions now; The problem is that your g doesn't define a symbolic function, so you can't use it as input to piecewise: sage: g(x) ... TypeError: unable to simplify to float approximation. You can manually define a symbolic function whose numeric evaluation is