On Mar 31, 11:40 am, "ma...@mendelu.cz" wrote:
> Dear Sage developers
>
> var('h1')._maxima_() returns a binomial coefficient instead of 'h1'.
> I was not find an explanation for this behavior in sage/interfaces and
> sage/symbolic. Do you have any explanation for this (I think
> unintended) beha
> andrejv wrote:
> > On Jan 10, 6:15 pm, Harald Schilly wrote:
> > > Hi, I got this from the report a problem link:
>
> > > Typing (in the inotebook)
>
> > > var('t,k,i')
> > > sum(binomial(i+t,t),i,0,k)
>
> > > results i
On Jan 15, 9:37 am, William Stein wrote:
> On Thu, Jan 14, 2010 at 10:43 PM, andrejv wrote:
>
> > On Jan 15, 6:14 am, Craig Citro wrote:
> >> Yeah, this is wacky. I can tell you why it's happening, though someone
> >> who's ever used Maxima before
On Jan 15, 6:14 am, Craig Citro wrote:
> Yeah, this is wacky. I can tell you why it's happening, though someone
> who's ever used Maxima before should really think about the right fix.
> Here's the issue: in sage.calculus.calculus, there's an instance of
> Maxima that gets created and passed the
On Jan 10, 6:15 pm, Harald Schilly wrote:
> Hi, I got this from the report a problem link:
>
> Typing (in the inotebook)
>
> var('t,k,i')
> sum(binomial(i+t,t),i,0,k)
>
> results in
>
> binomial(k + t + 1, t + 1) - 1
>
> which is false, the well-known answer is binomial(k + t + 1, t + 1)
There is
On Dec 10, 12:39 pm, "ma...@mendelu.cz" wrote:
> On 10 pro, 11:02, Harald Schilly wrote:
>
> > > (%i3) ratsimp(a), algebraic=true;
>
> > Ok, is it wise to do this by default if called from sage?
>
> Not sure (could it break something in integration for example?) but
> without this we have bug des
On Dec 10, 6:21 am, kcrisman wrote:
> On Dec 9, 5:07 pm, Harald Schilly wrote:
>
>
>
> > Hi, i got a "report a problem" comment about how
> > simplify/full_simplify works. I think this could be sent to maxima
> > upstream?
>
> > Well, here is the (rather educational) example:
>
> > sage: a=(sqrt(
On 24 avg., 08:52, William Stein wrote:
> OK, that is very valuable to know. It means that independent of
> Sage, just evaluating the same expression "1+2" in Maxima repeatedly
> quickly leads to dramatic slowdowns. This seems to me like an
> absolutely huge bug in Maxima.
>
> I did another te
