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 conflicts? Best, Anne On 7/16/12 9:49 AM, 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. I can assure you that all > jokes about deprecating the deprecations have already been made. > > What needs to be done is switch this: > > from sage.misc.misc import deprecation > deprecation('description', 'Sage version X') > > to > > from sage.misc.superseded import deprecation > deprecation(ticket_number, 'description') > > where ticket_number is an integer, the trac ticket number. If you have any > questions, I'd be happy to help. -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
