BTW, that "magic" commit also fixes #25252.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send em
On Thursday, April 26, 2018 at 2:55:49 PM UTC+2, Erik Bray wrote:
>
> Thanks for checking! Wow, I would not have guessed that. Do you have
> any idea if problem is fixed in general, or just in that one case?
>
I have no idea what the general problem is (except that mul::eval is prone
to loops
Thanks for checking! Wow, I would not have guessed that. Do you have
any idea if problem is fixed in general, or just in that one case?
It's not immediately obvious to me how this fixes it. I'll open a
ticket either way.
On Wed, Apr 25, 2018 at 2:51 PM, Ralf Stephan wrote:
> By bisection I fin
By bisection I find the issue is fixed with the commit
https://github.com/pynac/pynac/commit/c4b2a4a42c6f01f0db6c3d54d493a049806e
which fixes a power problem and apparently prevents the extraction of 2
mentioned earlier.
Anyway please open a ticket for the doctest.
Regards,
--
You received
On Wed, Apr 25, 2018 at 10:45 AM, Ralf Stephan wrote:
> On Tuesday, April 24, 2018 at 5:15:17 PM UTC+2, Erik Bray wrote:
>>
>> sqrt(2) * ((I - 1)*sqrt(2) - 2)
>>
>> Then for some reason it decides there's an overall coeffecient of -2!,
>
>
> That is probably what should be fixed.
>
>> and rewrites
Note also that the master branch of Pynac on github is not the same code as
the Pynac in Sage, although mul.cpp has not changed since. But there may
have been distant changes with side effects. For example 0.7.19 as in
#24838 with rc3 does not crash.
--
You received this message because you ar
On Tuesday, April 24, 2018 at 5:15:17 PM UTC+2, Erik Bray wrote:
>
> sqrt(2) * ((I - 1)*sqrt(2) - 2)
>
> Then for some reason it decides there's an overall coeffecient of -2!,
>
That is probably what should be fixed.
and rewrites the expression as:
>
> -2*sqrt(2)*(-(1/2*I - 1/2)*sqrt(2) + 1)
On Tue, Apr 24, 2018 at 5:23 PM, Jean-Pierre Flori wrote:
> It might be an issue with the "printing" order which is used to sort stuff
> in pynac internally (but not in orignal ginac) and we already had issues
> with in the past.
Yes, there is a comment in there (the first part added by rws):
7
It might be an issue with the "printing" order which is used to sort stuff
in pynac internally (but not in orignal ginac) and we already had issues
with in the past.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
On Tue, Apr 24, 2018 at 4:52 PM, Jean-Pierre Flori wrote:
> Ok I finally ended up in pynac code.
> It seems there is a bad recursion happening, with the following reversed
> backtrace:
> (Sage.)Expression._mul_
> Ginac::*
> Ginac::exmul
> Ginac::ex::ex
> Ginac::ex::construct_from_basic
> Ginac::mu
Ok I finally ended up in pynac code.
It seems there is a bad recursion happening, with the following reversed
backtrace:
(Sage.)Expression._mul_
Ginac::*
Ginac::exmul
Ginac::ex::ex
Ginac::ex::construct_from_basic
Ginac::mul::eval
Ginac::ex::ex
Ginac::ex::construct_from_basic
Ginac::mul::eval
...
G
Kind of strange, running sage -gdb I never end up in Expression._mul_ but
at random places in Python code.
On Tuesday, April 24, 2018 at 2:40:50 PM UTC+2, Frédéric Chapoton wrote:
>
> Amusing.. Also hangs on
>
> sage: (1/e1)/e2
> 1/2*sqrt(2)/((I - 1)*sqrt(2) - 2)
> sage: 1/_
>
>
> Le mardi 24 avr
Amusing.. Also hangs on
sage: (1/e1)/e2
1/2*sqrt(2)/((I - 1)*sqrt(2) - 2)
sage: 1/_
Le mardi 24 avril 2018 14:10:04 UTC+2, Erik Bray a écrit :
>
> Hi all,
>
> In working on an unrelated topic I encountered an indefinite hang,
> which I narrowed down to the following exact operation (I haven't
13 matches
Mail list logo
