-
-
Notifications
You must be signed in to change notification settings - Fork 589
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
Do not try to create embedded number field morphisms for non-embedded number fields #15331
Comments
Branch: u/SimonKing/ticket/15331 |
New commits:
|
Commit: |
Author: Simon King |
comment:3
Hi Simon, I'm trying to review this ticket, but there are a couple of things I don't understand:
Sorry if these are stupid questions, I'm still trying to learn how this all works! My attempt at simplifying the code based on these remarks is at |
comment:6
Replying to @mezzarobba:
Any remark on this Simon? If you're too busy, I'll just have a look for myself and try to take some action to get this merged. |
comment:7
Hi Jean-Pierre and Marc, Replying to @jpflori:
Sorry, I don't recall, and at the moment I am too much occupied with other things.
Yes, unless I wanted to see if the pushout exists in each step (catching the error if it does not exist).
So do I (now) ;-)
Sorry, I am. Best regards, Simon |
comment:8
I'm ok with Marc changes. My only concern is that it might be the case that previously catched errors are not anymore, only ValueError are. |
Changed branch from u/SimonKing/ticket/15331 to u/jpflori/ticket/15331 |
Changed author from Simon King to Simon King, Marc Mezzarobba |
Reviewer: Marc Mezzarobba, Jean-Pierre Flori |
comment:9
I've just added some doc about which ambient field is tried by default. If nobody feels concerned as I do about the uncatched errors (maybe the coercion framework already deals with them in a correct way, it just too late to try to remember about that), the let's get this merged. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
Replying to @jpflori:
Hmm,
Since no one seems to know in what scenarios these except clauses are supposed to be used (and the patches + tickets they come from do not make it clear to me), I thought we could remove them for now and add them back later, with tests triggering them, if necessary. But please feel free to change back the code to catch more exceptions if you disagree. |
comment:13
Replying to @mezzarobba:
Oops, in fact, I took back the description with what I built on top of the original Simon branch, and there I tried CDF last.
I agree with that plan. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed author from Simon King, Marc Mezzarobba to Simon King, Marc Mezzarobba, Jean-Pierre Flori |
Changed branch from u/jpflori/ticket/15331 to |
The attempt to create an embedded number field morphisms for non-embedded number fields currently fails (and should of course fail).
However, instead of running into an infinite recursion, a quick and simple
ValueError
(or perhapsTypeError
) should be raised.CC: @jpflori
Component: number fields
Author: Simon King, Marc Mezzarobba, Jean-Pierre Flori
Branch/Commit:
2bedaa1
Reviewer: Marc Mezzarobba, Jean-Pierre Flori
Issue created by migration from https://trac.sagemath.org/ticket/15331
The text was updated successfully, but these errors were encountered: