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
wrong category for parent of composition of number field endomorphisms #23647
Comments
comment:1
Travis, can you help, please ? This prevents from using richcmp for number fields morphisms. |
comment:2
So the problem comes down to this:
The source of which, when you go down
The latter should be
does not pass |
comment:3
Do you have branch for what you tried ? |
comment:4
No, I don't as it didn't work. However, I basically just added this to class NumberFieldHomset(RingHomset_generic): # This was already there
def __init__(self, R, S, category=None):
if category is None:
from sage.categories.number_fields import NumberFields
category = NumberFields()
RingHomset_generic(self, R, S, category) and the other variant I tried was def __init__(self, R, S, category=None):
if category is None:
category = R.category()
RingHomset_generic(self, R, S, category) |
comment:5
I have made another try, that causes interesting doctest failures:
EDIT: ok, ok. This is indeed a group. |
comment:6
Here is my branch. New commits:
|
Commit: |
Branch: public/23647 |
comment:7
in vanilla sage:
and |
comment:8
This does work, but it is a very big hack IMO. I think it might be worth trying to do a more comprehensive fix. At least as a first step, we can put QQ in |
comment:9
I believe |
comment:10
let us see what the patchbots say New commits:
|
Changed branch from public/23647 to public/23647-v2 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
This seems to work (somehow But
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
Here is another tentative, let us see what patchbot says. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
Green patchbot. Travis, do you think that this is good enough ? We could also try to find the best category given the target category.. |
Author: Frédéric Chapoton |
comment:18
I think it improves things and is fairly close to a proper (IMO) fix of determining the category directly from the input. We can worry about doing more if this becomes an issue again somewhere else. |
Reviewer: Travis Scrimshaw |
Changed branch from public/23647-v2 to |
namely
The last one should be the same as the other ones..
CC: @tscrim
Component: number fields
Author: Frédéric Chapoton
Branch/Commit:
768891b
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/23647
The text was updated successfully, but these errors were encountered: