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
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
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
