Re: [sage-devel] upgrading numpy/scipy

2014-05-28 Thread Volker Braun
On Wednesday, May 28, 2014 1:59:17 AM UTC+1, John H Palmieri wrote: > > I think that if you do "sage -i git_trac", it should install it for you. > Works but will give you an older version. It should work, but if you run into problems you should try the newest version first. Also, it'll be erase

Re: [sage-devel] upgrading numpy/scipy

2014-05-27 Thread François Bissey
On Tue, 27 May 2014 17:59:17 John H Palmieri wrote: > On Tuesday, May 27, 2014 5:06:16 PM UTC-7, François wrote: > > On Wed, 14 May 2014 06:57:53 Volker Braun wrote: > > > On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry > > > > > > (sage-googlesucks@xxx) wrote: > > > > In short, what is the

Re: [sage-devel] upgrading numpy/scipy

2014-05-27 Thread John H Palmieri
On Tuesday, May 27, 2014 5:06:16 PM UTC-7, François wrote: > > On Wed, 14 May 2014 06:57:53 Volker Braun wrote: > > On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry > > > > (sage-googlesucks@xxx) wrote: > > > In short, what is the git command to get a summary of the changes > related >

Re: [sage-devel] upgrading numpy/scipy

2014-05-27 Thread François Bissey
On Wed, 14 May 2014 06:57:53 Volker Braun wrote: > On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry > > (sage-googlesucks@xxx) wrote: > > In short, what is the git command to get a summary of the changes related > > to a package > > git log build/pkgs/ > > git trac find > > Various combin

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread François Bissey
On Wed, 14 May 2014 06:57:53 Volker Braun wrote: > On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry > > (sage-googlesucks@xxx) wrote: > > In short, what is the git command to get a summary of the changes related > > to a package > > git log build/pkgs/ > > git trac find > I am guessing t

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread Volker Braun
On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry (sage-googlesucks@xxx) wrote: > > In short, what is the git command to get a summary of the changes related > to a package git log build/pkgs/ git trac find Various combinations could also be scripted but I don't really see the need, ie.

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread William Stein
On May 13, 2014 7:13 PM, "François Bissey" wrote: > > On Tue, 13 May 2014 18:52:03 William Stein wrote: > > On Tue, May 13, 2014 at 6:43 PM, François Bissey > > > > wrote: > > > On Tue, 13 May 2014 18:30:26 William Stein wrote: > > >> On Tue, May 13, 2014 at 6:23 PM, François Bissey > > >> > > >>

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread Francois Bissey
Dear me, the subject appeared a few times when other packages were changed and on discussion of the git workflow but this one seems to be the straw that broke the camel's back. On 14/05/2014, at 22:54, Thierry wrote: > On Wed, May 14, 2014 at 01:43:24PM +1200, François Bissey wrote: > [...] >

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread Thierry
On Wed, May 14, 2014 at 01:43:24PM +1200, François Bissey wrote: [...] > I know that the squashing of the changelog in the new style sage is > unpopular in some quarters but I am sticking to the official line. I am not sure a hole in the documentation can serve as "the official line", could you

Re: [sage-devel] upgrading numpy/scipy

2014-05-14 Thread Volker Braun
Feel free to write a patch if you care about it. On Wednesday, May 14, 2014 2:52:03 AM UTC+1, William wrote: > > I'm no big fan of the SPKG.txt changelog, which always seemed > redundant to me. But if we're going to officially get rid of them, > why not just get rid of all of them at once? > >

Re: [sage-devel] upgrading numpy/scipy

2014-05-13 Thread François Bissey
On Tue, 13 May 2014 18:52:03 William Stein wrote: > On Tue, May 13, 2014 at 6:43 PM, François Bissey > > wrote: > > On Tue, 13 May 2014 18:30:26 William Stein wrote: > >> On Tue, May 13, 2014 at 6:23 PM, François Bissey > >> > >> wrote: > >> > Hi all, > >> > > >> > If someone is interested in

Re: [sage-devel] upgrading numpy/scipy

2014-05-13 Thread kcrisman
> > > > Is that intentional? For example, these lines get deleted forever: > > > > Yes. > > > > I've never been a huge fan of SPKG.txt being our change log, rather > > than just the revision history. However, the fact is that SPKG.txt is > > an important part of documenting the change hist

Re: [sage-devel] upgrading numpy/scipy

2014-05-13 Thread William Stein
On Tue, May 13, 2014 at 6:43 PM, François Bissey wrote: > On Tue, 13 May 2014 18:30:26 William Stein wrote: >> On Tue, May 13, 2014 at 6:23 PM, François Bissey >> >> wrote: >> > Hi all, >> > >> > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage, >> > they can review http://tra

Re: [sage-devel] upgrading numpy/scipy

2014-05-13 Thread François Bissey
On Tue, 13 May 2014 18:30:26 William Stein wrote: > On Tue, May 13, 2014 at 6:23 PM, François Bissey > > wrote: > > Hi all, > > > > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage, > > they can review http://trac.sagemath.org/ticket/16299 > > I glanced at it for a second an

Re: [sage-devel] upgrading numpy/scipy

2014-05-13 Thread William Stein
On Tue, May 13, 2014 at 6:23 PM, François Bissey wrote: > Hi all, > > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage, > they can review http://trac.sagemath.org/ticket/16299 I glanced at it for a second and noticed that [1] completely deletes the entire SPKG.txt change histo

[sage-devel] upgrading numpy/scipy

2014-05-13 Thread François Bissey
Hi all, If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage, they can review http://trac.sagemath.org/ticket/16299 I usually review package upgrades but I cannot review myself obviously. Francois -- You received this message because you are subscribed to the Google Groups "sa