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
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
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
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
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
+1 for just implementing lazy strings in the sage library.
Using speaklater for SAGE_TEMP is completely outside of the scope of the
upstream project. Its unlikely that we would contribute anything thats
useful for translations upstream, nor would we benefit from any further
translation specifi
David Roe writes:
> [ ] Import speaklater from sagenb
I should also mention, this doesn't literally mean import speaklater
*from* sagenb, since speaklater is not inside sagenb. It would just look
like::
import speaklater
Again, speaklater is just another separate PyPI package, like babel,
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
David Roe writes:
> http://wstein.org/home/keshav/files/speaklater-1.2-fbc7a37.spkg
I've upgraded to 1.3 which was released two days ago on my request. It
contains a fix for a problem which was noticed in sagenb last year. The
first SPKG I made used a development version of the code (commit fbc7a
William Stein writes:
> 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 #131
David Roe writes:
> 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 every use of temporary files within the sage library, or
> 2. depend on the speaklater project and use a lazy strin
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
>
>
> >> 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
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
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
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 every use of temporary files within the sage library, or
> 2. depend
16 matches
Mail list logo
