-
-
Notifications
You must be signed in to change notification settings - Fork 514
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
Cannot create homomorphism from prime residue field to finite field #11319
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Attachment: trac_11319_prime_field_coercion.patch.gz |
Author: Johan Bosman |
comment:3
I was trying out the patch, and the following example didn't work out like I expected:
Should this patch fix this as well? |
comment:4
In your example, you're trying to send the generator of k to the element 1 of F, which does indeed not define a field homomorphism. This does work:
|
Reviewer: Kiran Kedlaya |
comment:5
Looks fine, applies against 4.7, no long doctest failures. |
comment:6
I think the new patch is a bit low on examples. For example, the ticket mentions number fields, so why not add a number field example? |
Work Issues: examples |
Attachment: trac_11319_number_field_example.patch.gz To be used on top of the first patch |
comment:7
Example added. ;) |
Changed work issues from examples to none |
Changed reviewer from Kiran Kedlaya to Kiran Kedlaya, Michiel Kosters |
Merged: sage-4.8.alpha6 |
Changed keywords from residue fields, finite fields, hom to residue fields, finite fields, hom, sd35 |
Consider K = QQ(sqrt(337)). The prime 5 is inert in K and the prime 13 splits. We'll start with 13 to see what goes wrong:
However, for residue fields that aren't prime fields it does work:
Btw, this is in sage 4.6.2. on Mac OS 10.6.7.
Component: coercion
Keywords: residue fields, finite fields, hom, sd35
Author: Johan Bosman
Reviewer: Kiran Kedlaya, Michiel Kosters
Merged: sage-4.8.alpha6
Issue created by migration from https://trac.sagemath.org/ticket/11319
The text was updated successfully, but these errors were encountered: