-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
quo_rem in the polynomial rings does not use canonical coercion #383
Milestone
Comments
comment:3
Typo: arithmatic --> arithmetic |
comment:4
Attachment: 383-binop-decorator.patch.gz Oops. Thanks, fixed. |
comment:5
I read the code. Looks AWESOME! It appears to expose numerous issues:
|
Attachment: 383-fixes.patch.gz |
comment:6
OK, I've fixed all the above doctests issues. |
comment:7
Ut oh:
|
comment:8
Attachment: 383-more-fixes.patch.gz OK, I've doctested the entire sage library this time. |
Merged: sage-4.3.1.rc2 |
Author: Robert Bradshaw |
Reviewer: William Stein |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm looking at the polynomial function quo_rem and I see that it does it's own
coercion manually. This feels a little wrong to me. I think it should go
through the standard coercion routines. Here's a "bug" that results:
The bug is that I don't see why these two things are treated substantially
differently. The reason I found this is because the simple "TypeError"
exception did not provide the usual message about parents being
mis-matched -- I think this is a bug in itself
The fix for all that is to make the quo_rem stuff use canonical coercion model.
All of the quo_rem instances in sage/rings/polynomial/polynomial_element_generic.py suffer from some sort of coercion impropriety.
Component: basic arithmetic
Author: Robert Bradshaw
Reviewer: William Stein
Merged: sage-4.3.1.rc2
Issue created by migration from https://trac.sagemath.org/ticket/383
The text was updated successfully, but these errors were encountered: