Re: [sage-combinat-devel] The deprecation change

On Wed, Aug 01, 2012 at 04:54:45PM -0700, Volker Braun wrote: >Also, my personal patch queue is now almost as long as >sage-combinat so I'm very aware of the limitations. Glad to see we are not the only ones abusing queues :-) Which makes me thing that I know one of the Mercurial contribu

Re: [sage-combinat-devel] The deprecation change

On Wed, Aug 01, 2012 at 04:54:45PM -0700, Volker Braun wrote: >In general all your objections are already dealt with by the deprecation >framework, its just that in this exceptional / self-referential case it >didn't work. Fine. I'm open for constructive suggestions, but you haven't >

Re: [sage-combinat-devel] The deprecation change

On Wednesday, August 1, 2012 6:05:44 PM UTC-7, Volker Braun wrote: > > On Wednesday, August 1, 2012 8:47:37 PM UTC-4, John H Palmieri wrote: >> >> See . There may be >> other similar tickets by the same author. >> > > At least that ticket only tou

Re: [sage-combinat-devel] The deprecation change

On Wednesday, August 1, 2012 8:47:37 PM UTC-4, John H Palmieri wrote: > > See . There may be other > similar tickets by the same author. > At least that ticket only touches stuff in sage/misc and only replaces them by equivalent python 3. So it sh

Re: [sage-combinat-devel] The deprecation change

On Wednesday, August 1, 2012 1:35:02 PM UTC-7, Nicolas M. Thiery wrote: > > > All in all, in the future, I *will* put a negative review to similar > non essential global changes that impact much of "our" code (stuff in > combinat, ...). Unless the author volunteers to handle all the > rebasin

Re: [sage-combinat-devel] The deprecation change

Followups to sage-flame... In general all your objections are already dealt with by the deprecation framework, its just that in this exceptional / self-referential case it didn't work. Fine. I'm open for constructive suggestions, but you haven't given any. In the end, this patch is about making

Re: [sage-combinat-devel] The deprecation change

Dear Volker, On Mon, Jul 16, 2012 at 10:33:34AM -0700, Volker Braun wrote: >I've rebased http://trac.sagemath.org/5457 on top of the deprecation >change and it was a very easy change. Sure a very easy change. But this is to be multiplied by the number of patches. I for myself was

Re: [sage-combinat-devel] The deprecation change

Thanks, but this was really unnecessary since a more updated version of the patch is on the sage-combinat queue (where it is under development) and that one needs to be updated (not the one on trac). Best regards, Anne On 7/16/12 10:33 AM, Volker Braun wrote: > I've rebased http://trac.sagemat

Re: [sage-combinat-devel] The deprecation change

I've rebased http://trac.sagemath.org/5457 on top of the deprecation change and it was a very easy change. On Monday, July 16, 2012 12:53:52 PM UTC-4, Anne Schilling wrote: > > Dear Volker, > > The ticket http://trac.sagemath.org/5457 uses many deprecation warnings. > I tried to make your cha

Re: [sage-combinat-devel] The deprecation change

Hi Anne! On Mon, Jul 16, 2012 at 09:53:52AM -0700, Anne Schilling wrote: > Would it be ok to move to sage-5.2.rc0 and have the queue apply > there to avoid the conflicts? That's fine for me, but this would mean that all the Sage Days 40 newcomers from last week will need to instantly upda

Re: [sage-combinat-devel] The deprecation change

On Mon, Jul 16, 2012 at 09:49:47AM -0700, Volker Braun wrote: >The change in the deprecation framework (http://trac.sagemath.org/10508) >has been merged into sage-5.2.rc0. This is likely to break any patches >that are using deprecations. Sight ... Oh well, let us all count and report

Re: [sage-combinat-devel] The deprecation change

Dear Volker, The ticket http://trac.sagemath.org/5457 uses many deprecation warnings. I tried to make your change last week, but then it breaks the entire sage-combinat queue. Dear Sage-combinat developers, Would it be ok to move to sage-5.2.rc0 and have the queue apply there to avoid the conf

[sage-combinat-devel] The deprecation change

The change in the deprecation framework (http://trac.sagemath.org/10508) has been merged into sage-5.2.rc0. This is likely to break any patches that are using deprecations. I can assure you that all jokes about deprecating the deprecations have already been made. What needs to be done is switch