On Nov 8, 10:30 am, Michael Orlitzky wrote:
> On 11/08/11 10:05, kcrisman wrote:
>
>
>
> > Ah, that is luckily easy to fix! Just name your file
>
> > piecewise_test.sage
>
> > and all will be forgiven.
>
> I've tried this before, and gave up out of frustration. Most of my code
> is stored in di
On 11/08/11 10:05, kcrisman wrote:
>
>
> Ah, that is luckily easy to fix! Just name your file
>
> piecewise_test.sage
>
> and all will be forgiven.
I've tried this before, and gave up out of frustration. Most of my code
is stored in different modules and imported into little executable
script
On Nov 8, 9:58 am, Michael Orlitzky wrote:
> On 11/08/11 09:53, kcrisman wrote:
>
>
>
> > Note that this goes away if you instead define
>
> > sage: f0(x) = 4.0*(x-0.5)^2
>
> > (I mean after restarting Sage; the deprecation warning only will show
> > up once in any case.)
>
> I've got this in a
On 11/08/11 09:53, kcrisman wrote:
>
> Note that this goes away if you instead define
>
> sage: f0(x) = 4.0*(x-0.5)^2
>
> (I mean after restarting Sage; the deprecation warning only will show
> up once in any case.)
I've got this in a standalone python file, not running through the sage
prompt.
On Nov 8, 9:09 am, Michael Orlitzky wrote:
> On 11/07/11 21:03, kcrisman wrote:
>
>
>
> > So are you saying that Python and Piecewise functions will no longer
> > behave correctly if this behavior goes from warning to error? It
> > would be great if you had a "toy" example with full code; maybe
On 11/07/11 21:03, kcrisman wrote:
>
> So are you saying that Python and Piecewise functions will no longer
> behave correctly if this behavior goes from warning to error? It
> would be great if you had a "toy" example with full code; maybe there
> is a workaround that needs to become standard pr
On 11/07/11 21:03, kcrisman wrote:
>
> So are you saying that Python and Piecewise functions will no longer
> behave correctly if this behavior goes from warning to error? It
> would be great if you had a "toy" example with full code; maybe there
> is a workaround that needs to become standard pr
> There's a potential problem with piecewise:
>
> $ ./iterated-2d-solution.py
> ./iterated-2d-solution.py:85: DeprecationWarning: Substitution using
> function-call syntax and unnamed arguments is deprecated and will be
> removed from a future release of Sage; you can use named arguments
>
As to William and Jason's points about plot, yes, that is true (and
makes sense to me - we don't have to have ONLY one way to do it,
though we don't have to be like Perl either). I'm referring to some
situations where I run into this on worksheets, and I'm sure others do
as well.
Maybe it's just
On 11/7/11 3:05 PM, kcrisman wrote:
On Nov 7, 3:00 pm, William Stein wrote:
Hi,
Twice in the last day I've hit this deprecation warning due to making
a stupid typo:
sage: d(N) = (1/2)*(N^2-1)(N^2-N)/(N-1) # contains stupid typo
/Users/wstein/sage/install/current/local/lib/python2.6/si
On 11/7/11 2:00 PM, William Stein wrote:
Hi,
Twice in the last day I've hit this deprecation warning due to making
a stupid typo:
sage: d(N) = (1/2)*(N^2-1)(N^2-N)/(N-1) # contains stupid typo
/Users/wstein/sage/install/current/local/lib/python2.6/site-packages/IPython/iplib.py:2073:
Depr
On Mon, Nov 7, 2011 at 1:05 PM, kcrisman wrote:
>
>
> On Nov 7, 3:00 pm, William Stein wrote:
>> Hi,
>>
>> Twice in the last day I've hit this deprecation warning due to making
>> a stupid typo:
>>
>> sage: d(N) = (1/2)*(N^2-1)(N^2-N)/(N-1) # contains stupid typo
>> /Users/wstein/sage/insta
On Nov 7, 3:00 pm, William Stein wrote:
> Hi,
>
> Twice in the last day I've hit this deprecation warning due to making
> a stupid typo:
>
> sage: d(N) = (1/2)*(N^2-1)(N^2-N)/(N-1) # contains stupid typo
> /Users/wstein/sage/install/current/local/lib/python2.6/site-packages/IPytho
> n/ipl
13 matches
Mail list logo
