Re: [sage-devel] Re: Trying to make sense of how sage uses GP

2015-01-30 Thread Julien Puydt
Bonsoir, Le 30/01/2015 22:08, Nils Bruin a écrit : On Friday, January 30, 2015 at 7:31:29 AM UTC-8, Snark wrote: Snark, sent: sage[4]=0; Snark, sent: sage[5]=gen(sage[4]); Snark, sent: sage[6]=gen(); Snark, sent: sage[7]=_an_element_; Snark, sent: sage[8]=pi; This is from sage.structure.pare

Re: [sage-devel] .one() vs .one_element()

2015-01-30 Thread Jonas Jermann
Hi Vincent, Ok, I checked (with abstract space elements) and everything seems to work fine! :-) +1 Best Jonas On 30.01.2015 20:15, Vincent Delecroix wrote: Hi Jonas, All test pass within my branch. So at least nothing broken which is doctested. If you are worried about more, you should

[sage-devel] Re: Trying to make sense of how sage uses GP

2015-01-30 Thread Nils Bruin
On Friday, January 30, 2015 at 7:31:29 AM UTC-8, Snark wrote: > > Snark, sent: sage[4]=0; > Snark, sent: sage[5]=gen(sage[4]); > Snark, sent: sage[6]=gen(); > Snark, sent: sage[7]=_an_element_; > Snark, sent: sage[8]=pi; > This is from sage.structure.parent_old.pyx, line 376: "cdef _an_eleme

Re: [sage-devel] .one() vs .one_element()

2015-01-30 Thread Vincent Delecroix
Hi Jonas, All test pass within my branch. So at least nothing broken which is doctested. If you are worried about more, you should test it with my branch applied. Note that the three files that are of your concern are modified modular/modform_hecketriangle/abstract_ring.py modular/modf

Re: [sage-devel] .one() vs .one_element()

2015-01-30 Thread Jonas Jermann
Hi Just for your information: When I implemented modular forms spaces (with module elements that still have a multiplication/etc defined) I had to add both methods. one() to allow to take the power 0 of an element and one_element() to allow to take negative powers of elements. I hope everything

[sage-devel] Re: Trying to make sense of how sage uses GP

2015-01-30 Thread Nils Bruin
On Friday, January 30, 2015 at 7:31:29 AM UTC-8, Snark wrote: > > sage: gp('2+2') > Snark, sent: sage=vector(1024,k,0); > Snark, sent: sage[1]=2+2; > Snark, sent: print(sage[1]) > 4 > sage: gp('9+6') > Snark, sent: sage[2]=9+6; > Snark, sent: print(sage[2]) > 15 > sage: 2*gp(2) > Snark, s

[sage-devel] Trying to make sense of how sage uses GP

2015-01-30 Thread Julien Puydt
Hi, I'm now trying to understand how sage and GP interface, and much like with ECL+Maxima, I'll definitely need some help. I modified src/sage/interfaces/expect.py so I could peek at what gets sent to gp ; here is a short three-commands session : sage: gp('2+2') Snark, sent: sage=vector(102

Re: [sage-devel] Re: .one() vs .one_element()

2015-01-30 Thread Vincent Delecroix
#17694: needs review Would be cool to have it for sage-6.5 2015-01-30 12:15 UTC+01:00, Nathann Cohen : >> +1 to using .zero() and .one() and to deprecating .zero_element() and >> .one_element(). > +1 > > Nathann > > -- > You received this message because you are subscribed to the Google Groups >

Re: [sage-devel] A 'pip' issue

2015-01-30 Thread Thierry
Hi, note that a new version of openssl is available, and a trivial ticket (that needs review) could be merged before 6.5 at http://trac.sagemath.org/ticket/17691 Ciao, Thierry On Thu, Jan 29, 2015 at 03:28:14PM +0100, Nathann Cohen wrote: > Hello, > > > actually, the issue is a licensing one.

[sage-devel] Re: LinearModelFit contribution

2015-01-30 Thread rafaellopezfernandez
*Please forget the last part of the previous note. I was handling a very old version of find_fit. I have taken a new one and will try to make the changes to increase functionality on it.* El viernes, 30 de enero de 2015, 13:13:18 (UTC+1), rafaellope...@gmail.com escribió: > > I've tried to foll

[sage-devel] Re: LinearModelFit contribution

2015-01-30 Thread rafaellopezfernandez
I've tried to follow Volker's suggestion and prepare a python object for this purpose. However, I found a problem that I cannot manage. I must warn that my programming skills in python are rather limited (to say the less) and, therefore, I wouldn't be surprised if it were a silly issue. The fa

Re: [sage-devel] Re: .one() vs .one_element()

2015-01-30 Thread Nathann Cohen
> +1 to using .zero() and .one() and to deprecating .zero_element() and > .one_element(). +1 Nathann -- 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+un

[sage-devel] Re: .one() vs .one_element()

2015-01-30 Thread Samuel Lelievre
+1 to using .zero() and .one() and to deprecating .zero_element() and .one_element(). -- 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...@googl

Re: [sage-devel] bug report: "interval graph recognition"

2015-01-30 Thread Nathann Cohen
> This is a bug report from a Sage user... He also sent me an email. The bug report is correct, I'll see what happens. Nathann -- 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

[sage-devel] .one() vs .one_element()

2015-01-30 Thread Vincent Delecroix
Hello, It seems to me that we have aliases .one() and .one_element() on some parents (idem with zero). Do we have a policy concerning: - which one should be as an alias of the other? - should we deprecate one of the usage? I remember that I already discussed with Nicolas the fact that one_elemen

[sage-devel] getting a PyCharm professional license for us

2015-01-30 Thread Ralf Stephan
Hello, I'm using IDEs for development and recently tried PyCharm which turned out to be a big improvement vs. Eclipse. They have a free version (Python) and an unfree which additionally supports Cython. They offer no-money licenses on the unfree version for regular participants of Open Source proj