-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
fix _test_category for polynomial rings #15232
Comments
Branch: u/saraedum/ticket/15232 |
Author: Julian Rueth |
Changed branch from u/saraedum/ticket/15232 to u/roed/ticket/15232 |
Commit: |
comment:4
I've rebased this against sage-6.0 + #12555. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
There are some failing doctests, see patchbot report. |
Changed branch from u/roed/ticket/15232 to u/saraedum/ticket/15232 |
Changed keywords from none to sd59 |
comment:12
I am not sure anymore what I tried to do at this ticket. The new branch seems to fix this issue with only very few changes. New commits:
|
comment:13
Patchbot reports doctest failures. |
comment:26
Looks good to me. |
Changed work issues from conflicts to none |
Changed reviewer from Vincent Delecroix to Vincent Delecroix, David Roe |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:28
Thanks. |
comment:29
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:33
Looks good. |
Changed branch from public/ticket/15232 to |
Polynomial rings whose elements are not extension classes currently don't pass the TestSuite:
The problem is that polynomials do not use
element_class
to construct their elements but a_polyonmial_class
which does not use theElementMethods
of the category.Component: categories
Keywords: sd59
Author: Julian Rueth
Branch/Commit:
83ab7c3
Reviewer: Vincent Delecroix, David Roe
Issue created by migration from https://trac.sagemath.org/ticket/15232
The text was updated successfully, but these errors were encountered: