-
-
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
Finite field relative #34992
base: develop
Are you sure you want to change the base?
Finite field relative #34992
Conversation
a first draft that tries to restore some sanity in the factory code mostly
…n' into finite-field-relative
as it interferes with the one we inhertit from the general ring extension.
so it does not interfere with code inherited from the general extension framework
with Python 3 we'd see the underlying error. However, at the moment it's quite annoying that we cannot see what caused the ValueError.
…n' into finite-field-relative
so a few more extensions work (again)
polynomial.change_ring(R) produces a polynomial over R even if R is a polynomial ring (and even if R is polynomial.parent()) in the same way polynomial.change_ring(hom) now produces a polynomial over hom.codomain()
for the sake of testing GitLab Web IDE
…into finite-field-relative
…ev/sage into finite-field-relative
…into finite-field-relative
…nto ring-extensions-revisions
…te-field-relative
Adding implementation keyword to rings/morphisms
Documentation preview for this PR is ready! 🎉 |
Keep which methods? |
Sorry! I post my message in the wrong PR. (I used for the first time yesterday the command |
…finite-field-relative
…finite-field-relative
…finite-field-relative
…te-field-relative
Fixes #28485.