[sage-devel] Re: Sage part of Google's Summer of Code 2013

Ok, i can be that backup mentor if nobody else is interested. Although not a very reliable one (i don't even have a windows box available to test). Even so, i will help as much as i can. I just got an email communicating me that harald schilly wanted to grant me the role of mentor, but it pointed

Re: [sage-devel] Re: Sage part of Google's Summer of Code 2013

On Tue, Apr 9, 2013 at 12:58 PM, mmarco wrote: > I just got an email communicating me that harald schilly wanted to > grant me the role of mentor, but it pointed me to a link to accept > it... and there was no link at all in the email. > > Can you try to send it to my gmail account? hmpf, great.

[sage-devel] Using Sage's new doc builder outside the devel/sage tree?

Hi! For my p_group_cohomology spkg, that will soon have a new version, I am currently using a modified version of Sage's old doc builder to build the documentation. Now, as Sage's doc builder has changed, I wonder: Is it possible to call Sage's doc builder on .rst, .pyx and .py files outside of t

[sage-devel] Re: Using Sage's new doc builder outside the devel/sage tree?

On Tuesday, April 9, 2013 4:29:08 AM UTC-7, Simon King wrote: > > Hi! > > For my p_group_cohomology spkg, that will soon have a new version, I am > currently using a modified version of Sage's old doc builder to build > the documentation. > > Now, as Sage's doc builder has changed, I wonder:

[sage-devel] Re: Using Sage's new doc builder outside the devel/sage tree?

Hi John, On 2013-04-09, John H Palmieri wrote: > I don't think it is currently possible. I tried working on this a few > months ago: see . It works > for .py files but not .pyx files, and I never tracked down the problem. > Working on .rst files

[sage-devel] Mercurial refuses to access to combinat.sagemath.org

Dear All, I'm stuck on the following agravating problem: hg refuses to connect to combinat: popcorn-*oved/.hg/patches $ hg --debug pull -u using http://combinat.sagemath.org/patches/ sending capabilities command abort: error: Connection reset by peer or popcorn-/tmp $ hg --debug clone htt

[sage-devel] cpdef (a little) harmful

Sometimes one ends up with implementing really small access routines, just to do a lookup for something. In cython you might even want to do that with some "cdef" methods. For general accessibility, you might consider slapping a "cpdef" on rather than a "cdef". That may come at a serious price, bec

Re: [sage-devel] cpdef (a little) harmful

This shouldn't really come as a surprise. From the Cython documentation, "This is about 20 times slower, but still about 10 times faster than the original Python-only integration code. This shows how large the speed-ups can easily be when whole loops are moved from Python code into a Cython modul

[sage-devel] matrix multiplication weird coercion

I came across some behavior with matrix multiplication that doesn't seem very intuitive to me. N=matrix(QQ,[[1,1],[0,1]]) T=matrix(GF(7),[[1,1],[0,1]]) L=N*T L,L.parent() produces ([0 0] [0 0], Full MatrixSpace of 2 by 2 dense matrices over Ring of integers modulo 1) I tried to search for the

[sage-devel] Re: cpdef (a little) harmful

On Apr 9, 1:18 pm, Tom Boothby wrote: > This shouldn't really come as a surprise.  From the Cython documentation, > > "This is about 20 times slower, but still about 10 times faster than > the original Python-only integration code. This shows how large the > speed-ups can easily be when whole loop

[sage-devel] Re: matrix multiplication weird coercion

Hey, I'm pretty sure that's a bug since there is no coercion map between QQ and GF(7) ( which is different than calling GF(7)(1/5) ). Here's some of the other tests I tried: sage: T=matrix(GF(7),[[1,1],[0,3]]) sage: (N*T).parent() Full MatrixSpace of 2 by 2 dense matrices over Ring of integer

Re: [sage-devel] Re: matrix multiplication weird coercion

I think this issue is addressed at #8335, which I haven't had time to review David On Tue, Apr 9, 2013 at 3:52 PM, Travis Scrimshaw wrote: > Hey, >I'm pretty sure that's a bug since there is no coercion map between QQ > and GF(7) ( which is different than calling GF(7)(1/5) ). Here's so

[sage-devel] Re: matrix multiplication weird coercion

This may help: sage: sage.matrix.action.MatrixMatrixAction(N.parent(),T.parent()).codomain() Full MatrixSpace of 2 by 2 dense matrices over Ring of integers modulo 1 sage: A=matrix(GF(25,'a'),[[1,1],[0,3]]) sage: sage.matrix.action.MatrixMatrixAction(N.parent(),A.parent()).codomain() sage: G=N.par

Re: [sage-devel] Re: matrix multiplication weird coercion

Nope. With the three patches in #8335, I'm still getting the same behavior on sage 5.8. Could you double check me on that? If there isn't anywhere else that this is fixed in, I can open a separate bug. On Tuesday, April 9, 2013 5:54:55 PM UTC-4, David Roe wrote: > > I think this issue is addres

Re: [sage-devel] Re: cpdef (a little) harmful

On Tue, Apr 9, 2013 at 1:44 PM, Nils Bruin wrote: > Since it is entirely unclear from that tutorial what the factor 20 (or > the factor 10) refers to, I would not have understood that code to > mean "even the fastest path of a cpdef function is slower than a > cdef". There is a lot of documentati

Re: [sage-devel] Re: cpdef (a little) harmful

On Tue, Apr 9, 2013 at 1:44 PM, Nils Bruin wrote: > On Apr 9, 1:18 pm, Tom Boothby wrote: >> This shouldn't really come as a surprise. From the Cython documentation, >> >> "This is about 20 times slower, but still about 10 times faster than >> the original Python-only integration code. This show

[sage-devel] Re: cpdef (a little) harmful

On Apr 9, 4:11 pm, Robert Bradshaw wrote: > To let x.foo() call different functions depending on whether your in > Cython or Python, or even worse whether x is fully typed, would be > even more surprising. Does cython overload on type signature? I don't have a particular problem with the semantic

Re: [sage-devel] Re: cpdef (a little) harmful

On Tue, Apr 9, 2013 at 5:26 PM, Nils Bruin wrote: > On Apr 9, 4:11 pm, Robert Bradshaw > wrote: >> To let x.foo() call different functions depending on whether your in >> Cython or Python, or even worse whether x is fully typed, would be >> even more surprising. > > Does cython overload on type s