On Sat, Jan 1, 2011 at 6:09 PM, kcrisman wrote:
> Happy New Year as well!
>
> Certainly sometimes we do simply remove methods which are used
> absolutely nowhere in the code and are clearly for internal use only.
> The way you describe this certainly make them seem like a candidate
> for this.
I
On Mon, Nov 23, 2009 at 02:19:14AM +0100, Florent hivert wrote:
> 1 - Add an option called ``version`` do deprecation where you can put the
> information on since which version of sage this thing was deprecated:
>
> sage: def bar():
> ...sage.misc.misc.deprecation("The function
On Nov 23, 2009, at 1:22 PM, Jason Grout wrote:
> Florent Hivert wrote:
> Of course, when writing code, we have no idea what date the next
> release
> would be, and sometimes are mistaken about the release that the
> patch
> will be included in as well. How should we take ca
> >> Of course, when writing code, we have no idea what date the next
> >> release
> >> would be, and sometimes are mistaken about the release that the patch
> >> will be included in as well. How should we take care of this
> >> patch-updating problem?
> >
> > I've been lazy to raise this proble
On Nov 23, 2009, at 9:23 AM, Florent Hivert wrote:
> Hi Jason
>
>>> Speaking about deprecation, I posted a patch #7515 which does two
>>> things:
>>>
>>> 1 - Add an option called ``version`` do deprecation where you can
>>> put the
>>> information on since which version of sage this thing
Hi Jason
> > Speaking about deprecation, I posted a patch #7515 which does two things:
> >
> > 1 - Add an option called ``version`` do deprecation where you can put the
> > information on since which version of sage this thing was deprecated:
> >
> > sage: def bar():
> > ..
> > Speaking about deprecation, I posted a patch #7515 which does two things:
> >
> > 1 - Add an option called ``version`` do deprecation where you can put the
> > information on since which version of sage this thing was deprecated:
> >
> > sage: def bar():
> > ... sage.misc.misc.
On Sun, Nov 22, 2009 at 5:19 PM, Florent Hivert
wrote:
> Hi there,
>
>> Regarding deprecation, we already hashed this out in a previous thread
>> quite some time ago.
>>
>> * Use the official deprecation(...) function when deprecating a function.
>>
>> * We can tell precisely what is depr
Hi there,
> Regarding deprecation, we already hashed this out in a previous thread
> quite some time ago.
>
> * Use the official deprecation(...) function when deprecating a function.
>
> * We can tell precisely what is deprecated and when by simply
> looking at the source code and usi
On Tue, Nov 03, 2009 at 09:30:50AM -0800, William Stein wrote:
> * "Sage is very incoherent in its design from one part to the other."
>
> Which parts? From my perspective, Sage is very *coherent* because
> essentially all of the things I use a lot I designed! But the
> perspective is completel
10 matches
Mail list logo
