Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread Volker Braun
On Wednesday, July 4, 2012 11:27:17 PM UTC+1, Michael Orlitzky wrote: > > 6 Principle of least surprise: most (all?) other external projects > are distributed as SPKGs, so this one should be too unless there's > a good reason not to. > If you rummage around in sage.misc then I think y

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread Michael Orlitzky
On 07/04/2012 06:07 PM, William Stein wrote: > On Wed, Jul 4, 2012 at 11:45 AM, Michael Orlitzky > wrote: >> On 07/03/12 23:06, Keshav Kini wrote: >>> >>> IMO it's usually better to depend on someone else's code than to absorb >>> it, because then you can more easily pick up bugfixes later, and a

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread R. Andrew Ohana
On Wed, Jul 4, 2012 at 3:07 PM, William Stein wrote: > Added the code as an spkg or to the Sage library unchanged (without > adding doctests) is equivalent from this perspective. Code put in the > sage library as a file unchanged is no more or less "absored" than > code put in an spkg. > I dis

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread William Stein
On Wed, Jul 4, 2012 at 11:45 AM, Michael Orlitzky wrote: > On 07/03/12 23:06, Keshav Kini wrote: >> >> IMO it's usually better to depend on someone else's code than to absorb >> it, because then you can more easily pick up bugfixes later, and also it >> makes it clearer that we are benefiting from

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread Michael Orlitzky
On 07/03/12 23:06, Keshav Kini wrote: > > IMO it's usually better to depend on someone else's code than to absorb > it, because then you can more easily pick up bugfixes later, and also it > makes it clearer that we are benefiting from their work. To choose > absorbing code instead of depending on

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-04 Thread Julien Puydt
Le 04/07/2012 05:06, Keshav Kini a écrit : IMO it's usually better to depend on someone else's code than to absorb it, because then you can more easily pick up bugfixes later, and also it makes it clearer that we are benefiting from their work. To choose absorbing code instead of depending on it

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-03 Thread John H Palmieri
On Tuesday, July 3, 2012 11:45:11 AM UTC-7, Justin C. Walker wrote: > > > On Jul 3, 2012, at 11:33 , John H Palmieri wrote: > > > > > > > On Tuesday, July 3, 2012 10:55:21 AM UTC-7, David Roe wrote: > >> > >> Hi everyone, > >> The new doctesting code (#12415) needs a change to the way Sage

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-03 Thread kcrisman
> > > >> Everyone working on the ticket thinks option 2 is the way to go. > >> Speaklater consists of a single python file and is already used in the > new > >> flask notebook (#11080) by including the python file. Rather than > introduce > >> a strange dependency of sage on the notebook or

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-03 Thread Justin C. Walker
On Jul 3, 2012, at 11:33 , John H Palmieri wrote: > > > On Tuesday, July 3, 2012 10:55:21 AM UTC-7, David Roe wrote: >> >> Hi everyone, >> The new doctesting code (#12415) needs a change to the way Sage handles >> temporary files, which is described at #13147. We can either >> 1. change ever

Re: [sage-devel] Re: Vote: adding speaklater as a standard spkg

2012-07-03 Thread William Stein
On Tue, Jul 3, 2012 at 11:33 AM, John H Palmieri wrote: > > > On Tuesday, July 3, 2012 10:55:21 AM UTC-7, David Roe wrote: >> >> Hi everyone, >> The new doctesting code (#12415) needs a change to the way Sage handles >> temporary files, which is described at #13147. We can either >> 1. change eve