Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Andrea Lazzarotto
Ok sorry, probably I was confusing with the revised BSD and the fact that the license happily allows proprietary software to use and abuse open source components. But yes, you are right about the single files. -- Andrea Lazzarotto -- To post to this group, send an email to sage-devel@googlegroup

[sage-devel] Re: sage release plan

2012-06-29 Thread Jason Grout
On 6/29/12 4:30 PM, Andrea Lazzarotto wrote: Il giorno 29/giu/2012 23:20, "Jason Grout" mailto:jason-s...@creativetrax.com>> ha scritto: > The BSD files themselves would still be BSD, even if the distribution was GPL, right? You can't just delete the BSD header and change it to GPL, can you? Y

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Andrea Lazzarotto
Il giorno 29/giu/2012 23:20, "Jason Grout" ha scritto: > The BSD files themselves would still be BSD, even if the distribution was GPL, right? You can't just delete the BSD header and change it to GPL, can you? You can change a single character and release your modified version as GPL. :-) -- A

[sage-devel] Re: sage release plan

2012-06-29 Thread Jason Grout
On 6/29/12 4:13 PM, Jeroen Demeyer wrote: On 2012-06-29 20:54, Fernando Perez wrote: On Fri, Jun 29, 2012 at 11:46 AM, Jan Groenewald wrote: Would this symmetric flow not also be possible if ipython relicensed to GPL? Honest question. Certainly, but that's not in the cards. All the 'scipy e

[sage-devel] Re: sage release plan

2012-06-29 Thread Jason Grout
On 6/29/12 1:54 PM, Fernando Perez wrote: It would be likely impossible to get them to agree to a GPL relicensing. But you wouldn't have to, right? You could just add one file that was GPL, and start distributing that, and IPython would switch to GPL (though the files already there would be

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Jeroen Demeyer
On 2012-06-29 20:54, Fernando Perez wrote: > On Fri, Jun 29, 2012 at 11:46 AM, Jan Groenewald wrote: >> Would this symmetric flow not also be possible if ipython relicensed to GPL? >> Honest question. > > Certainly, but that's not in the cards. All the 'scipy ecosytem' > (python, numpy, scipy, m

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Andrea Lazzarotto
> > Besides at this > point even if I wanted (which I don't) to change it I couldn't, as > there are by now way too many ipython contributors who made their > contributions to the project as BSD. It would be likely impossible to > get them to agree to a GPL relicensing. > Can't it be an issue for

[sage-devel] Re: Pyrex-mode vs Cython-mode

2012-06-29 Thread Keshav Kini
Ivan Andrus writes: > Actually Cython itself comes with cython-mode.el [1], so perhaps we > ought to use that. IMO this is clearly the way to go :) -Keshav Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe fro

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Fernando Perez
On Fri, Jun 29, 2012 at 11:46 AM, Jan Groenewald wrote: > Would this symmetric flow not also be possible if ipython relicensed to GPL? > Honest question. Certainly, but that's not in the cards. All the 'scipy ecosytem' (python, numpy, scipy, matplotlib, ipython, pandas, statsmodels, scikit-learn

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Jan Groenewald
Hi On 29 June 2012 20:39, Fernando Perez wrote: > Minor note from the peanut gallery: > > On Wed, Jun 27, 2012 at 10:46 AM, William Stein wrote: > > We should just relicense the sage notebook as BSD to completely > > eliminate this problem > > speaking from the IPython side, this would be great

Re: [sage-devel] Re: sage release plan

2012-06-29 Thread Fernando Perez
Minor note from the peanut gallery: On Wed, Jun 27, 2012 at 10:46 AM, William Stein wrote: > We should just relicense the sage notebook as BSD to completely > eliminate this problem speaking from the IPython side, this would be great for us. We're starting to have real collaboration between ipy

[sage-devel] Review "deprecation to use trac ticket" patch

2012-06-29 Thread Volker Braun
It would be great if somebody could review this. It doesn't involve any math, and the design decisions were already discussed on the mailinglist. And it would make my life easier since the patch is going to break whenever a deprecation is added/removed from the Sage library. http://trac.sagemat

Re: [sage-devel] sage release plan

2012-06-29 Thread Jeroen Demeyer
On 2012-06-29 13:51, kcrisman wrote: > Is it dependent on the number of betas? That seems to have been the > determining factor in the last year or so. Yes, probably this is the most important factor. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this

Re: [sage-devel] sage release plan

2012-06-29 Thread kcrisman
On Friday, June 29, 2012 2:49:44 AM UTC-4, Jeroen Demeyer wrote: > > On 2012-06-28 23:20, kcrisman wrote: > > Okay, but to play devil's advocate - if the explicit goal is merging > > #11080 and releasing something without problems otherwise, could that > > take shorter? > I really doubt it wo

[sage-devel] Pyrex-mode vs Cython-mode

2012-06-29 Thread Ivan Andrus
I'm updating sage-mode to work with the latest python.el, so I'm going through it systematically for the time. I've noticed something odd, namely that there exist both pyrex-mode and cython-mode. cython-mode is very minimal, and a strict subset of pyrex-mode. However, both register themselves

[sage-devel] Re: Consistency of comparison of finite field elements

2012-06-29 Thread Simon King
Hi! Apparently we use three essentially different ways of comparing matrices: sage: def test(K): : M1 = Matrix(K,[[1,0,0]]) : M2 = Matrix(K,[[0,1,0]]) : M3 = Matrix(K,[[0,1,1]]) : M4 = Matrix(K,[[0,0,1]]) : L = [M1,M2,M3,M4] : L.sort()

[sage-devel] Upgrade to mercurial-2.2.2 (#13175) needs review

2012-06-29 Thread Jeroen Demeyer
I created an upgraded mercurial spkg, mainly because the current one doesn't work properly on Solaris SPARC and that's annoying for Sage development. I added a small sanity check in spkg-install that "hg log" works on the mercurial spkg repository. So please review: http://trac.sagemath.org/sage_