Re: [sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Jeroen Demeyer
On 2014-01-13 17:16, Simon King wrote: On 2014-01-13, Jeroen Demeyer wrote: It was deprecated since 3 years and removed. Use sig_on() and sig_off() instead. Thanks! I suppose using sig_on() will work on any Sage version that is younger than 2 years old, then? I want that my spkg not only buil

[sage-devel] Re: The lcm of two univariate polynomials

2014-01-13 Thread Nils Bruin
On Monday, January 13, 2014 4:32:10 PM UTC-8, Gregory Bard wrote: > > Hi everyone. I might be confused but I think I've found something not > quite right. > > The following code: > > ### > a(x) = x^2 - 5*x + 6 > b(x) = x^2 - 8*x + 15 > For polynomial arithmetic, you're

[sage-devel] Update the "Download Source" page

2014-01-13 Thread Volker Braun
http://www.sagemath.org/download-source.html doesn't mention git, but does contain a link to hg.sagemath.org. It would be great if somebody could update that page. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group an

[sage-devel] The lcm of two univariate polynomials

2014-01-13 Thread Gregory Bard
Hi everyone. I might be confused but I think I've found something not quite right. The following code: ### a(x) = x^2 - 5*x + 6 b(x) = x^2 - 8*x + 15 f(x) = lcm( a(x), b(x) ) print f print f.rational_simplify() ### produces the output

Re: [sage-devel] Re: Python as build-time dependency

2014-01-13 Thread François Bissey
On Sun, 12 Jan 2014 21:15:21 Volker Braun wrote: > At the risk of veering even further off-topic, I would like to give up > "tree relocation" as it is currently defined. Its cumbersome (need to check > that we haven't been moved all the time) and insecure. > > For relocatable binaries, we build wi

Re: [sage-devel] Re: Python as build-time dependency

2014-01-13 Thread Michael Orlitzky
On 01/12/2014 02:06 PM, Felix Salfelder wrote: > On Sun, Jan 12, 2014 at 01:09:42PM -0500, Michael Orlitzky wrote: >> Prefix is designed to run as an ordinary user on non-gentoo systems. If >> you're on gentoo, you don't need it (unless you don't have root). Plenty >> of us have been able to get it

[sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Simon King
On 2014-01-13, Jeroen Demeyer wrote: > It was deprecated since 3 years and removed. > Use sig_on() and sig_off() instead. Thanks! I suppose using sig_on() will work on any Sage version that is younger than 2 years old, then? I want that my spkg not only builds on the latest Sage version. Best re

Re: [sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Jeroen Demeyer
On 2014-01-13 16:54, Simon King wrote: Another question: Has something happened with _sig_on? It was deprecated since 3 years and removed. Use sig_on() and sig_off() instead. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from th

[sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Simon King
On 2014-01-13, Simon King wrote: > Is SAGE_INCLUDE missing? Another question: Has something happened with _sig_on? Now, after fixing the paths (so that interrupt.pxi can be included), _sig_on can not be found. Best regards, Simon -- You received this message because you are subscribed to the G

[sage-devel] SPARC debug

2014-01-13 Thread Volker Braun
I've once again wasted days trying to debug something on SPARC until I realized that debug builds just segfault left and right. Steps to reproduce: CFLAGS='-O0 -g' ./sage -f pari sage -bt src/sage/libs/pari # lots of segfaults How can we compile with debugging information? And if not, how can

[sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Simon King
Hi Jeroen, On 2014-01-13, Jeroen Demeyer wrote: > I would start by trying to fix the hardcoded paths in src/setup.py in > your package (using SAGE_SRC). I see: There are more variables than SAGE_SRC: SAGE_LOCAL, SAGE_EXTCODE, ... Is SAGE_INCLUDE missing? Best regards, Simon -- You received

[sage-devel] Re: How to includ interrupt.pxi?

2014-01-13 Thread Simon King
Hi Jeroen, On 2014-01-13, Jeroen Demeyer wrote: > I would start by trying to fix the hardcoded paths in src/setup.py in > your package (using SAGE_SRC). By "hardcoded", you mean the paths relative to SAGE_ROOT? So, replacing SAGE_ROOT by SAGE_SRC would solve the problem (in most cases at least)

Re: [sage-devel] How to includ interrupt.pxi?

2014-01-13 Thread Jeroen Demeyer
On 2014-01-13 14:10, Simon King wrote: Hi! My optional p_group_cohomology spkg does not install with sage-6.1.b4. Problem (for now): The package contains Cython code, and in some .pxd files I do include "interupt.pxi" This used to work, but fails now. I see that in the sage sources some .p

[sage-devel] How to includ interrupt.pxi?

2014-01-13 Thread Simon King
Hi! My optional p_group_cohomology spkg does not install with sage-6.1.b4. Problem (for now): The package contains Cython code, and in some .pxd files I do include "interupt.pxi" This used to work, but fails now. I see that in the sage sources some .pxd files do include "sage/ext/inte

[sage-devel] changing authentication method on ask.sagemath.org

2014-01-13 Thread Daniel Krenn
Hi, since myopenid will be hinstory soon, see [1] "MYOPENID WILL BE TURNED OFF ON 2/1/2014", I have to find a different method for signing in into ask.sagemath.org. Is there a a way to change this (keeping my profile)? Maybe I over-looked it. BTW: From mathoverflow.net and stackexchange/stackover

Re: [sage-devel] Creating a new branch

2014-01-13 Thread John Cremona
Thanks for the comments, and David's reassurance. I have marked the ticket as ready for review. John On 13 January 2014 12:20, David Roe wrote: > > > > On Mon, Jan 13, 2014 at 5:10 AM, John Cremona > wrote: >> >> The following surprised me. I wanted to work on ticket #10108 which >> had an ol

Re: [sage-devel] Creating a new branch

2014-01-13 Thread Jeroen Demeyer
On 2014-01-13 13:20, David Roe wrote: On Mon, Jan 13, 2014 at 5:10 AM, John Cremona mailto:john.crem...@gmail.com>> wrote: The following surprised me. I wanted to work on ticket #10108 which had an old patch (which no longer applies). Here is what I did: 1. I made sure that I

Re: [sage-devel] Creating a new branch

2014-01-13 Thread David Roe
On Mon, Jan 13, 2014 at 5:10 AM, John Cremona wrote: > The following surprised me. I wanted to work on ticket #10108 which > had an old patch (which no longer applies). Here is what I did: > > 1. I made sure that I was on the develop branch which was up-to-date. > 2. I did > sage -dev checkout

[sage-devel] Creating a new branch

2014-01-13 Thread John Cremona
The following surprised me. I wanted to work on ticket #10108 which had an old patch (which no longer applies). Here is what I did: 1. I made sure that I was on the develop branch which was up-to-date. 2. I did sage -dev checkout --ticket=10108 which worked fine, putting me into a new branch ca

Re: [sage-devel] Re: Python as build-time dependency

2014-01-13 Thread Jeroen Demeyer
On 2014-01-12 20:06, Felix Salfelder wrote: On Sun, Jan 12, 2014 at 01:09:42PM -0500, Michael Orlitzky wrote: Prefix is designed to run as an ordinary user on non-gentoo systems. If you're on gentoo, you don't need it (unless you don't have root). Plenty of us have been able to get it working, s