Re: [sage-devel] Re: Names of special methods like _pari_

2017-03-14 Thread William Stein
On Tue, Mar 14, 2017 at 12:38 PM, Luca De Feo wrote: > Hello, > > Discussion on this matter seems to have stalled, with no clear > consensus. There is an open ticket (#22470, only affecting _pari_) > that we would like to close by the end of SD85. > > Let me summarize the discussion. From what I'v

Re: [sage-devel] "replacement" optional packages

2017-03-14 Thread Dima Pasechnik
On Sunday, March 12, 2017 at 8:38:02 AM UTC, Jeroen Demeyer wrote: > > On 2017-03-12 09:35, Dima Pasechnik wrote: > > X11? > > That can be disabled with --disable-gui > this does not work, still (here is a slightly weird error I get on OSX (with Sage's gcc 5.4)): g++ -DPACKAGE_NAME=\"\" -DP

Re: [sage-devel] Re: Names of special methods like _pari_

2017-03-14 Thread Luca De Feo
Hello, Discussion on this matter seems to have stalled, with no clear consensus. There is an open ticket (#22470, only affecting _pari_) that we would like to close by the end of SD85. Let me summarize the discussion. From what I've read, the only two options that seem to have gained some consens

Re: [sage-devel] For the record : the lil' Win10 notebook that (almost) could (barely).

2017-03-14 Thread Erik Bray
On Fri, Mar 10, 2017 at 7:23 PM, Samuel Lelievre wrote: > Thu 2017-02-16 16:33:56 UTC+1, Emmanuel Charpentier: > >> Dear Erik, >> >> Le jeudi 16 février 2017 11:09:00 UTC+1, Erik Bray a écrit : >> >>> On Thu, Feb 16, 2017 at 8:26 AM, Emmanuel Charpentier wrote: >>> >>> > This is a followup on the

Re: [sage-devel] Re: PYTHONPATH breaks Python3

2017-03-14 Thread Erik Bray
On Sat, Mar 11, 2017 at 11:26 AM, Volker Braun wrote: > I noticed that, too. We should just remove it. I doesn't just break our own > python3, it also is a major pain if you want to use gdb to debug stuff > (which embeds python3 nowadays). +1 to this > On Saturday, March 11, 2017 at 1:28:52 AM U

Re: [sage-devel] Is anybody using set_coercion_model()?

2017-03-14 Thread John Cremona
On 14 March 2017 at 12:10, Jeroen Demeyer wrote: > The coercion model in Sage seems to be designed to allow it to be changed: > there is a global object coercion_model defined in element.pyx which can be > get/set using get_coercion_model() and set_coercion_model(). So *in theory* > it is possible

[sage-devel] Is anybody using set_coercion_model()?

2017-03-14 Thread Jeroen Demeyer
The coercion model in Sage seems to be designed to allow it to be changed: there is a global object coercion_model defined in element.pyx which can be get/set using get_coercion_model() and set_coercion_model(). So *in theory* it is possible to implement a different coercion model. However, i

[sage-devel] Desktop entry spec

2017-03-14 Thread Jan Groenewald
Hi A desktop icon is very useful on campus environments where sagemath notebook is used in courses on Linux boxes. https://trac.sagemath.org/ticket/22599 Regards, Jan -- .~. /V\ Jan Groenewald /( )\www.aims.ac.za ^^-^^ -- You received this message because you are subscribed to

[sage-devel] Re: Making package polymake optional

2017-03-14 Thread Travis Scrimshaw
No objections from me. Although we might want to try and improve the configure script before we make it optional if it can fail without helpful error messages. Best, Travis On Tuesday, March 14, 2017 at 2:54:19 AM UTC-5, vdelecroix wrote: > > Dear all, > > Now that we are in the process of ha

[sage-devel] Making package polymake optional

2017-03-14 Thread Vincent Delecroix
Dear all, Now that we are in the process of having a proper interface to polymake (see [1] thanks to Simon) I would propose to move the package polymake from experimental to optional. For those who don't know, polymake is a CAS focused on polytopes (and toric varieties) written in perl. An a