[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 w

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

On Monday, May 23, 2016 at 6:11:55 PM UTC-7, paulmasson wrote: > > With all due deference to the work that went into making piecewise > functions symbolic, it's too much overhead for purely numerical > applications, as for example WKB approximations. Here's some sample code >

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

Getting rid of resetwarnings in all places is ready for review at http://trac.sagemath.org/ticket/20667 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel

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

With all due deference to the work that went into making piecewise functions symbolic, it's too much overhead for purely numerical applications, as for example WKB approximations. Here's some sample code

[sage-devel] Re: Warnings traceback for top level

On Monday, 23 May 2016 16:22:58 UTC-6, Volker Braun wrote: > > Apparently the IPython/Jupyter devs don't want to change their deprecation > warnings and advise users to filter them out: > https://github.com/ipython/ipython/issues/9242. So something like > > warnings.filterwarnings('default', cate

[sage-devel] Re: Warnings traceback for top level

Apparently the IPython/Jupyter devs don't want to change their deprecation warnings and advise users to filter them out: https://github.com/ipython/ipython/issues/9242. So something like warnings.filterwarnings('default', category=DeprecationWarning, module='.*/mypackage/.*') should work if we

[sage-devel] Warnings traceback for top level

While IPython shows nice traceback for exceptions, even for 1/0 in the interpreter, it is quite confusing for warnings, e.g. novoselt@sage:~/sage$ sage ┌┐ │ SageMath version 7.3.beta0, Release Date: 2016-05-21 │ │ T

Re: [sage-devel] Re: Testing and consecutive spaces in output

On Monday, May 23, 2016 at 2:38:28 AM UTC-7, Jori Mäntysalo wrote: > > > https://docs.python.org/release/3.1.5/library/stdtypes.html#old-string-formatting-operations > > says "The formatting operations described here are obsolete and may go > away in future versions of Python." > ...and a few

[sage-devel] Re: On development workflows for sharing (experimental) code

Dear Sage developers, In: https://wiki.sagemath.org/CodeSharingWorkflow I suggested a variant of the pip package workflow for sharing code, where the features are dynamically inserted into the Sage library from code laid out as in the Sage library by recursive monkey patching.

Re: [sage-devel] wishlist: numpy ufuncs and Sage symbolic callable functions

On Fri, May 20, 2016 at 11:38 PM, William Stein wrote: > Hi Sage-Devel, > > I just spent the week teaching numpy and matplotlib in the context of > Sage. Walking around and watching why/how students got frustrated on > certain homework problems revealed one way we could improve Sage, > which woul

Re: [sage-devel] Python3

On Fri, May 20, 2016 at 8:04 PM, William Stein wrote: > Hi, > > Somebody with possibly substantial grant funds asked me today: "How > much might it cost to get Sage to work with Python3?" > > I don't know. Anybody have any thoughts? Is there anybody reading > this who wishes they could spend

Re: [sage-devel] Re: Testing and consecutive spaces in output

On Mon, 23 May 2016, John Cremona wrote: Are we not allowed to use print("x = %s" % x) any more? https://docs.python.org/release/3.1.5/library/stdtypes.html#old-string-formatting-operations says "The formatting operations described here are obsolete and may go away in future versions of Py

Re: [sage-devel] Re: Testing and consecutive spaces in output

On 23 May 2016 at 09:56, William Stein wrote: > On Mon, May 23, 2016 at 1:47 AM, John Cremona wrote: >> Are we not allowed to use >> >> print("x = %s" % x) >> >> any more? > > It works fine in python3. > > $ python3 > Python 3.5.1+ (default, Mar 30 2016, 22:46:26) > [GCC 5.3.1 20160330] on linux

Re: [sage-devel] Re: Testing and consecutive spaces in output

On Mon, May 23, 2016 at 1:47 AM, John Cremona wrote: > Are we not allowed to use > > print("x = %s" % x) > > any more? It works fine in python3. $ python3 Python 3.5.1+ (default, Mar 30 2016, 22:46:26) [GCC 5.3.1 20160330] on linux Type "help", "copyright", "credits" or "license" for more inform

Re: [sage-devel] Re: Testing and consecutive spaces in output

Are we not allowed to use print("x = %s" % x) any more? John On 23 May 2016 at 08:32, Jori Mäntysalo wrote: > On Mon, 23 May 2016, Travis Scrimshaw wrote: > >> As I understand it, extra whitespace is ignored by the doctester. > > > OK. Sounds mostly reasonable, but means of course that nice pr

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

On 2016-05-23 10:30, Jeroen Demeyer wrote: On 2016-05-23 00:03, Andrey Novoseltsev wrote: Why??? I think it's safe to assume that there is a good reason, it's just the way it was done historically. Sorry, I meant to say "I think it's safe to assume that there is *no* good reason"... -- Yo

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

On 2016-05-23 00:03, Andrey Novoseltsev wrote: Why??? I think it's safe to assume that there is a good reason, it's just the way it was done historically. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

Re: [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

Re: [sage-devel] Re: Testing and consecutive spaces in output

On Mon, 23 May 2016, Travis Scrimshaw wrote: As I understand it, extra whitespace is ignored by the doctester. OK. Sounds mostly reasonable, but means of course that nice printing of matrices can not be tested easily. -- Jori Mäntysalo

[sage-devel] Re: Testing and consecutive spaces in output

Hey Jori, As I understand it, extra whitespace is ignored by the doctester. Best, Travis On Monday, May 23, 2016 at 2:11:59 AM UTC-5, Jori Mäntysalo wrote: > > I just saw a ticket where > > print "x = ", x > > was changed to > > print("x = {}".format(x) > > i.e. for example "x = 42" is c

[sage-devel] Testing and consecutive spaces in output

I just saw a ticket where print "x = ", x was changed to print("x = {}".format(x) i.e. for example "x = 42" is changed to "x = 42". But testing went fine. So is there some logic that slightly modifies expected output before testing? If so, what else it does than sqeeze consecutive spaces?