[sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

Dear sage-devel, In my sage spkg, I have a cython file in which I use sig_check(). For that I need to add the following line at the top of the file: include "sage/ext/interrupt.pxi" # ctrl-c interrupt block support For cythonizing, I need to provide appropriate include libraries in the setup.

Re: [sage-devel] Exceptions format; keyword 'implementation'

On 2015-11-06 19:05, Jori Mäntysalo wrote: "backend" clearly refers to some bigger difference, like different data structure, and applies mostly to functions creating some object. Yes, I think this probably holds for "backend", "impl", "implementation" and "solver". I would vote to unify all the

[sage-devel] Re: Re: should "foo?" print TESTS: blocks or omit them?

Jori Mäntysalo wrote: >> And those edge cases should be documented. > > Maybe. But something like Graph().is_connected() is easy to check, if > the user wants to know if empty graph is defined to be connected. When there is no ambiguity in the method that will be called, yes. But as soon as you

Re: [sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

On 2015-11-07 09:17, Sébastien Labbé wrote: What should be the appropriate value for include_dirs? from sage.env import sage_include_directories include_dirs = sage_include_directories() -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubs

[sage-devel] Re: should "foo?" print TESTS: blocks or omit them?

[X] 'foo?' should NOT display TESTS blocks. [ ] 'foo?' should display TESTS block. -- Marc -- 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+unsubscr

[sage-devel] Re: should "foo?" print TESTS: blocks or omit them?

I don't really care about whether to display TESTS:: or not, but we really should have a proper parser for our docstring style. This ticket adds yet another regex hack. E.g. sphinxcontrib-napoleon is an example for how it is done correctly: * Nicer typeset output since the docbuilder has semant

Re: [sage-devel] Exceptions format; keyword 'implementation'

It seems that there is different opinion of exceptions format. See http://trac.sagemath.org/ticket/19542 . More views? (We need vote.sagemath.org. And this is not a joke. A www-service to make a query and to vote between options.) -- Jori Mäntysalo

[sage-devel] useful patchbot bookmark

Dear all, I just have made so that one can now use the following permanent bookmark to monitor the patchbot results on one's tickets: http://patchbot.sagemath.org/?base=develop&participant=was Replacing "was" by your own login will give results for tickets you have been involved in. It will a

Re: [sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

On Saturday, November 7, 2015 at 10:36:46 AM UTC+1, Jeroen Demeyer wrote: > > On 2015-11-07 09:17, Sébastien Labbé wrote: > > What should be the appropriate value for include_dirs? > > from sage.env import sage_include_directories > include_dirs = sage_include_directories() > This is exactly

[sage-devel] Re: Manifold equality and UniqueRepresentation

Hi Travis, On 2015-11-06, Travis Scrimshaw wrote: >> On 2015-11-05, Travis Scrimshaw > wrote: >> >I would then be advocating for using UniqueRepresentation if that was >> > the only issue. >> >> It really depends whether in comparing manifolds you would prefer to do >> *some* >> heuristi

Re: [sage-devel] Exceptions format; keyword 'implementation'

We should follow Python; this has an added benefit of typically keeping error messages more concise. Best, Travis On Saturday, November 7, 2015 at 4:36:04 AM UTC-6, Jori Mäntysalo wrote: > > It seems that there is different opinion of exceptions format. See > http://trac.sagemath.org/ticket/19

[sage-devel] doctest modifications in french sagebook

Hello, In the Sage trac ticket #19539, I changed the behavior of Graphics.plot and it turns out that one test in the french sagebook had to be changed. Vincent -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

On 2015-11-07 13:39, Sébastien Labbé wrote: This is exactly what I do, but I get the warning saying "_signals" is redefined. Yes, sorry, I didn't notice. Why is it redefined? Because of hackery in the signals code. I think this fixes it (feel free to open a ticket): diff --git a/src/sage/ex

[sage-devel] Change log web page not found

Hello, I start to make my sage 6.9 local install (my desktop comp x64 bits Ubuntu 14.04 LTS) and follow instructions at http://www.sagemath.org/download-source.html and in that web page, the URL link "changelog" in sentence "There is a very high level changelog

Re: [sage-devel] Re: sagemath 6.9 Ubuntu PPA: Error typesetting mathematics

Thanks! the suggested steps fixed the MathJax problem for the PPA install at our department. Other computer rooms at our university (outside our department, and with a different maintainer) also have SageMath 6.6 installed. Would you recommend to first uninstall 6.6 there, and then install 6.9, to

Re: [sage-devel] Re: sagemath 6.9 Ubuntu PPA: Error typesetting mathematics

Hi Samuel, Yes, as far as I know a purge and then an install will work. Please let me know. Regards, Jan On 7 November 2015 at 20:31, Samuel Lelievre wrote: > Thanks! the suggested steps fixed the MathJax problem for the PPA > install at our department. > > Other computer rooms at our universi

Re: [sage-devel] Exceptions format; keyword 'implementation'

> > We should follow Python; this has an added benefit of typically keeping > error messages more concise. > One very common occurrence of a long exception message are the PackageNotFoundError which happen when one calls a function which relies on a non-installed package: PackageNotFo

Re: [sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

On Saturday, November 7, 2015 at 6:13:14 PM UTC+1, Jeroen Demeyer wrote: > I think this fixes it (feel free > to open a ticket): > > diff --git a/src/sage/ext/interrupt/pxi.h b/src/sage/ext/interrupt/pxi.h > index b4bfe49..5f3c528 100644 > --- a/src/sage/ext/interrupt/pxi.h > +++ b/src/sag

Re: [sage-devel] What should be the include_dirs for a cython file using sig_check() outside of the sage library?

> > In any case, it's only a warning. The Sage library has the same problem > > but we compile with -w to ignore warnings. > > Ok I see. So the -w is an option to which command exactly? Not the same as > the one I use I guess (installing an spkg with sage -p). > It's a flag for gcc. David -- You

[sage-devel] Re: Manifold equality and UniqueRepresentation

Hey Simon, >> >I would then be advocating for using UniqueRepresentation if that > was > >> > the only issue. > >> > >> It really depends whether in comparing manifolds you would prefer to do > >> *some* > >> heuristics to detect homeomorphic manifolds, or prefer to consider > >> manifo

Re: [sage-devel] Re: Manifold equality and UniqueRepresentation

On Sat, Nov 7, 2015 at 6:28 PM, Travis Scrimshaw wrote: > Hey Simon, > > >> >I would then be advocating for using UniqueRepresentation if that >> was >> >> > the only issue. >> >> >> >> It really depends whether in comparing manifolds you would prefer to >> do >> >> *some* >> >> heuristics to

Re: [sage-devel] Exceptions format; keyword 'implementation'

On Sat, Nov 7, 2015 at 3:24 PM, Nathann Cohen wrote: > We should follow Python; this has an added benefit of typically keeping >> error messages more concise. >> > > One very common occurrence of a long exception message are the > PackageNotFoundError which happen when one calls a function which

Re: [sage-devel] Keyword 'implementation'

On Sat, 7 Nov 2015, Jeroen Demeyer wrote: "backend" clearly refers to some bigger difference, like different data structure, and applies mostly to functions creating some object. Yes, I think this probably holds for "backend", "impl", "implementation" and "solver". I would vote to unify all t

Re: [sage-devel] Keyword 'implementation'

Hello, > Maybe first thing could be change method -> algorithm? (With deprecation, of > course.) With a case-by-case check, however. The replacement you intend seems to work on most occurrences, but there is a Graph.show(method='js') that cannot be replaced with 'algorithm'. Nathann P.S.: I don