New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is_polynomial returns wrong results #11352
Comments
comment:1
We just return GiNaC's response:
|
comment:2
Replying to @vbraun:
So this probably must be reported to GiNaC, isn't it ? |
This comment has been minimized.
This comment has been minimized.
comment:5
I just installed a fresh GiNaC on my computer and I've been able to reproduce the bug:
gives
So I subscribed to ginac mailing list and reported the bug here. I'm waiting for an answer. Florent |
Upstream: Reported upstream. Little or no feedback. |
comment:6
Thanks for doing that, Florent. By the way, can you put a link to the thread on the Ginac list here? |
comment:7
Sure ! Here it is: http://www.ginac.de/pipermail/ginac-list/2011-May/001822.html |
comment:8
I just got the following answer:
I'm not sure what will happen next: Should we backport the fix or update the whole ginac ? |
Changed upstream from Reported upstream. Little or no feedback. to Reported upstream. Developers acknowledge bug. |
Work Issues: wait for upstream fix |
Changed work issues from wait for upstream fix to none |
comment:9
The bug seems to be fixed upstream, thanks to Richard B. Kreckel:
http://www.ginac.de/ginac.git?p=ginac.git;a=commitdiff;h=0c2f0f4c6d http://www.ginac.de/ginac.git?p=ginac.git;a=commitdiff;h=293ff6f6fe As I previously said, I'm not sure what to do next. Moreover, I'd rather let who knows about PyNaC and Sage symbolic internal handle the rests of this ticket. Please feel free to take ownership of it. |
Changed upstream from Reported upstream. Developers acknowledge bug. to Fixed upstream, in a later stable release. |
comment:10
Thanks for following this through so far Florent. The next step is for me to make a new Pynac release with these patches. I will do this in the next few days, but it might be a while before this lands in a Sage release, since the next version of pynac will include fixes for #9880 and an upstream patch for #10964. |
comment:11
Hi Burcin, Replying to @burcin:
I'm keeping an eye here. Count me as a volunteer if some help is needed for the review. |
comment:13
Attachment: trac_11352-is_polynomial.patch.gz From the Ginac mailing list:
So we now "only" need to upgrade ginac. There is no "fixed upstream and released" tag... I'm not sure if the current tag is correct. |
comment:14
I won't rant about the tags. :) Note that this is still Upstream is pynac in this case. I ported the patches in the GiNaC release to Pynac (this is easier than it sounds, you just ignore changes to files that don't exist), but didn't make a release yet. Here is the queue of patches which will be merged: |
Dependencies: #11415 |
comment:15
New pynac package which includes the patch for this is at #11415. attachment: trac_11352-is_polynomial.patch adds doctests. |
This comment has been minimized.
This comment has been minimized.
Author: Richard Kreckel, Jens Vollinga, Burcin Erocal |
comment:16
Positive review. |
Reviewer: Karl-Dieter Crisman |
This comment has been minimized.
This comment has been minimized.
comment:19
Oops, browser windows closed too fast - I was on #10964 still :) |
comment:20
Wiki markup here is different than on Sage wiki :( |
This comment has been minimized.
This comment has been minimized.
comment:21
Okay, now positive review! Good catch by rbk, incidentally, with the |
Merged: sage-4.7.1.alpha4 |
I definitely prefer to get
False
.Apply attachment: trac_11352-is_polynomial.patch.
Depends on #11415
Upstream: Fixed upstream, in a later stable release.
CC: @kcrisman @burcin @hivert @RBKreckel
Component: symbolics
Keywords: is_polynomial
Author: Richard Kreckel, Jens Vollinga, Burcin Erocal
Reviewer: Karl-Dieter Crisman
Merged: sage-4.7.1.alpha4
Issue created by migration from https://trac.sagemath.org/ticket/11352
The text was updated successfully, but these errors were encountered: