On Mon, Sep 12, 2011 at 10:18 PM, Dima Pasechnik wrote:
> I guess this all boils down to the point made by William - that _pow_ needs
> to be integrated into the coersion framework (currently it is not).
+1. Also, I should point out that I didn't make the decision myself
back then; I was sitting
I uniformized the behavior of 0^0 a long time ago (though I make no
claim about what has happened between then and now -- just that it was
uniform for a few precious minutes). The decision back then (which I
still stand behind) is that while it is mathematically unjustifiable,
it's Python's conven
I guess this all boils down to the point made by William - that _pow_ needs
to be integrated into the coersion framework (currently it is not).
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegr
Hi Jason,
This is really neat and I love the way the code view is integrated. I
was checking out the cell, and would suggest a version optimized for
handhelds.
Awesome work,
Alex Juarez
On Jul 29, 2011, at 2:11 PM, Jason Grout wrote:
> Hi everyone,
>
> I'd like to announce a trial beta run of a
Here some random examples of wich I find the first one the strangest
sage: CC(0)^CC(0)
NaN - NaN*I
sage: a=GF(7)(0)
sage: a^a
...
ArithmeticError: 0^0 is undefined.
sage: a=Integers(7)(0)
sage: a^a
...
ArithmeticError: 0^0 is undefined.
sage: K.=QQ[]
sage: K(0)^K(0)
1
sage: K.=QQ[sqrt(2)]
sag
> sage: SR(0^0)
> 1
Well, this is a red herring since 0^0 will evaluate, and SR(1) should
be 1. What about CDF or other more bizarre rings? But I agree with
you in principle.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email t
If one puts it this way:
sage: 0^0
1
sage: RDF(0)^RDF(0) #this one is the most dubious
1.0
sage: SR(0^0)
1
sage: SR(0)^SR(0)
RuntimeError: power::eval(): pow(0,0) is undefined
I think it's pretty clear that the error should go away unless there
are very convincing technical reasons.
--
To post
On Sep 12, 12:45 pm, Keshav Kini wrote:
> Hey Burcin,
>
> I guess that means you think that pynac should return 1 for 0^0, then? As
> opposed to making Sage throw a ValueError or something at
> Integer(0)^Integer(0) ?
>
I think that Sage has had 0^0 return 1 for quite some time now? On
the oth
Hey Burcin,
I guess that means you think that pynac should return 1 for 0^0, then? As
opposed to making Sage throw a ValueError or something at
Integer(0)^Integer(0) ?
I'll poke around :)
-Keshav
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this
Just printing the camera position would be a huge help! I have been
trying to figure out the same thing for a while now.
-Niles
p.s. Thanks Sébastian!!!
On Sep 10, 2:11 pm, Jonathan wrote:
> If you are doing everything through Sage, would having Jmol print the
> rotation information to the w
Hi Keshav,
On Mon, 12 Sep 2011 03:16:27 -0700 (PDT)
Keshav Kini wrote:
> I believe that error message is propagated from GiNaC. See line 523
> of src/ginac/power.cpp in the pynac spkg. The error message is
> hard-coded and doesn't refer to python's eval() function.
This should be fixed in pynac
On 12 sep, 12:16, Keshav Kini wrote:
> Hi Simon,
>
> I believe that error message is propagated from GiNaC. See line 523 of
> src/ginac/power.cpp in the pynac spkg. The error message is hard-coded and
> doesn't refer to python's eval() function.
You're definitely right.
>
> -Keshav
--
To post
It was renamed in revision ed738932ba96 (sequential number 14045 in my tree,
which I imagine should be the same for pretty much everyone else), to
sage/rings/finite_rings/element_givaro.pyx , where it currently remains,
just fyi. No idea why it's reappearing in your Sage, though.
-Keshav
Hi Simon,
I believe that error message is propagated from GiNaC. See line 523 of
src/ginac/power.cpp in the pynac spkg. The error message is hard-coded and
doesn't refer to python's eval() function.
-Keshav
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
Hi Keshav,
On 12 Sep., 11:30, Keshav Kini wrote:
> RuntimeError: power::eval(): pow(0,0) is undefined
That error message is an interesting statement, because it is wrong,
even in pure Python:
>>> pow(0,0)
1
The error message mentions "eval", but it doesn't seem to be eval's
fault either:
>>> e
Here is a sample:
sage: 0^0
1
sage: (x^x)(x=0)
---
RuntimeError Traceback (most recent call last)
/home/fs/ in ()
/opt/sage/local/lib/python2.6/site-packages/sage/symbolic/expression.so in
sage.
On 12 Sep., 11:05, leif wrote:
> After rebuilding Sage (not just the library), I somehow get this file
> back.
>
> It is empty, and according to Mercurial, it was last modified by #8220
> (but not deleted or renamed *there*).
>
> Any idea how or why this happens?
P.S.: This is not reproducible b
After rebuilding Sage (not just the library), I somehow get this file
back.
It is empty, and according to Mercurial, it was last modified by #8220
(but not deleted or renamed *there*).
Any idea how or why this happens?
-leif
--
To post to this group, send an email to sage-devel@googlegroups.c
On Sun, Sep 11, 2011 at 8:30 PM, John H Palmieri wrote:
>
>
> On Sunday, September 11, 2011 8:13:53 PM UTC-7, William wrote:
>>
>> On Sun, Sep 11, 2011 at 11:17 AM, John H Palmieri
>> wrote:
>> > When I log in to sage.math, I see the file
>> >
>> > /home/sagemath/www/packages/experimental/4ti2-
19 matches
Mail list logo
