On Tue, Feb 23, 2016 at 6:50 AM, Clemens Heuberger <clemens.heuber...@aau.at> wrote: > I am currently revising a paper that I submitted in March 2015. Parts of the > results heavily rely on computations in Sage; at that time, Sage 6.5. > > It turns out that the old code no longer works with Sage 7.0. It is also > impossible to compile Sage 6.5 nowadays because the infrastructure changed (it > tries to download > http://www.sagemath.org/packages/upstream/patch/patch-2.7.1.tar.gz which no > longer exists). For completeness I mention that none of my old code triggered > a > deprecation warning and that it worked 11 months ago.
Is this really the case? If we no longer provide tarballs that can be compiled without internet access, then this is a *massive* regression. > Bottom line: I cannot reproduce 11 month old results anymore. Adapting the > code > is a frustrating and lengthy work. No matter what -- even if you were going to update your code -- you would absolutely want to have access to a sage-6.5 build, so you could test before and after. > And it does not solve the problem, because > new releases of Sage will again introduce changes. > > At https://groups.google.com/d/msg/sage-devel/tDKb8QF97VY/tc8jFWDwQ2YJ, there > was some discussion on tests related to papers and books and the > src/sage/tests > directory. > > Of course, I could have opened a ticket and included my code into the > src/sage/tests directory. But I cannot imagine that this approach would scale > very well. I assume that there are many papers out there with a substantial > amount of CPU time required for reproducability. > > Any thoughts/suggestions? > > Regards, > > Clemens > >> -------- Original-Nachricht -------- >> Betreff: [sage-devel] tests related to papers and books >> Datum: Thu, 8 May 2014 15:38:10 -0700 >> Von: William Stein <wst...@gmail.com> >> Antwort an: sage-devel@googlegroups.com >> An: sage-devel <sage-devel@googlegroups.com> >> >> Hi, >> >> I'm at a reproducible research workshop, and that reminded me that we >> have a directory in Sage full of tests related to published works: >> >> https://github.com/sagemath/sage/tree/master/src/sage/tests >> >> But it's really not much at all! So if you're going to write (or >> wrote) a paper with Sage examples, try to remember to add a file to >> the above directory, so your examples work forever, etc. >> >> William >> >> > > -- > 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...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- William (http://wstein.org) -- 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...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
