-
-
Notifications
You must be signed in to change notification settings - Fork 488
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
Sage thinks that I^(2/3) = -1 #30783
Comments
comment:1
Hi Marc, could you please provide more details about this ticket ? Currently (9.2.rc2), we have:
|
comment:2
Sorry, I didn't have time yesterday. This happens for i ∈ ℚ[i], not i ∈ SR (see the linked ticket). But note that #18036 aims to make the glbal symbol i refer to the generator of ℚ[i]. (In fact, I am currently trying again to make that change, and that's how I discovered the issue.) |
comment:3
Oups, I made a mistake while reviewing #25218. Feel free to fix that to the correct thing. |
This comment has been minimized.
This comment has been minimized.
Author: Marc Mezzarobba |
Commit: |
Branch: u/mmezzarobba/30783-revert_25218 |
comment:5
I confirm with the branch I get this:
Bot is green (except for startup time which I think we can ignore because this ticket does not change anything regarding to that). |
Reviewer: Sébastien Labbé |
Changed branch from u/mmezzarobba/30783-revert_25218 to |
Revert #25218.
Rationale: #25218 makes
a^(p/q)
where a is a number field element attempt to return a solution toa^p = x^q
in the number field. This makes powering inconsistent with coercions, since number fields often (and, in the case of quadratic fields, automatically) come with a complex embedding and complex numbers of various kinds use the principal branch of the power function.Among other confusing behaviors, we have
but
and
but
as well as
CC: @BrentBaccala
Component: basic arithmetic
Author: Marc Mezzarobba
Branch/Commit:
0807787
Reviewer: Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/30783
The text was updated successfully, but these errors were encountered: