-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
complex_field.py complex_number.pyx -> complex_mpfr.pyx #24483
Comments
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet. |
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch: u/vdelecroix/24483 |
Author: Vincent Delecroix |
comment:3
patchbot not happy if Author is not given... |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:9
Can we just do the renaming without deprecation for now? That way, we wouldn't need the fix the Pynac. If possible, I would like to avoid Sage-specific patches to upstream projects. |
comment:10
Replying to @jdemeyer:
The whole point is precisely to start a deprecation... though for ease of review I can move the deprecation in another ticket. Would that be better? |
comment:12
All right. The import of |
This comment has been minimized.
This comment has been minimized.
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, in a later stable release. |
Changed upstream from Fixed upstream, in a later stable release. to none |
Dependencies: #24497 |
comment:16
Great! Thanks Ralf. I will put back the deprecation. |
comment:40
Replying to @mjungmath:
Thank you. I moved around the |
comment:41
The global variable Besides, this constant is already defined in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:43
Replying to @mjungmath:
True. Fixed in the last commit. |
comment:44
I think, this would be it from my side. When patchbot turns green, I can give a positive review. |
comment:45
Replying to @videlec:
Is it worth to investigate why this (former) "spurious" output is gone now? |
comment:46
This was a pretty bad doctest. It is removed in my commits diff --git a/src/sage/misc/citation.pyx b/src/sage/misc/citation.pyx
index 2de53c1..847f357 100644
--- a/src/sage/misc/citation.pyx
+++ b/src/sage/misc/citation.pyx
@@ -40,7 +40,7 @@ systems['NTL'] = ['sage.libs.ntl',
systems['FLINT'] = ['_flint']
systems['GMP'] = ['sage.rings.integer.Integer']
systems['MPFR'] = ['sage.rings.real_mpfr',
- 'sage.rings.complex_number']
+ 'sage.rings.complex_mpfr']
systems['MPFI'] = ['sage.rings.real_mpfi',
'sage.rings.complex_interval']
systems['M4RI'] = ['sage.matrix.matrix_mod2_dense']
@@ -80,15 +80,6 @@ def get_systems(cmd):
sage: I = R.ideal(x^2+y^2, z^2+y)
sage: get_systems('I.primary_decomposition()')
['Singular']
-
- Here we get a spurious ``MPFR`` because some coercions need to be
- initialized. The second time it is gone::
-
- sage: a = var('a')
- sage: get_systems('((a+1)^2).expand()')
- ['MPFR', 'ginac']
- sage: get_systems('((a+1)^2).expand()')
- ['ginac']
"""
import cProfile, pstats, re |
comment:47
Replying to @videlec:
Thanks. Removing the test seems sensible. However, I just ask myself why this ticket has that effect. Perhaps it is worth to investigate it? |
comment:48
It might be complicated to track down precisely... with no reward as far as I can see. |
comment:49
Patchbot morally green. LGTM. |
comment:50
Thank you! |
Reviewer: Michael Jung |
Changed branch from u/vdelecroix/24483 to |
comment:53
Hi Vincent, What would you think of keeping files |
Changed commit from |
comment:54
Definitely (with deprecated lazy imports)! |
comment:55
Could you open a ticket? |
comment:56
→ #30857 |
, sagemath#24483, sagemath#24371, sagemath#24511, sagemath#25848, sagemath#26105, sagemath#28481, sagemath#29010, sagemath#29412, sagemath#30332, sagemath#30372, sagemath#31345, sagemath#32375, sagemath#32606, sagemath#32610, sagemath#32612, sagemath#32641, sagemath#32660, sagemath#32750, sagemath#32869, sagemath#33602 <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes sagemath#1234" use "Introduce new method to calculate 1+1" --> <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> <!-- If this PR resolves an open issue, please link to it here. For example "Fixes sagemath#12345". --> <!-- If your change requires a documentation PR, please link it appropriately. --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [ ] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on - sagemath#12345: short description why this is a dependency - sagemath#34567: ... --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#36307 Reported by: Matthias Köppe Reviewer(s):
In order to uniformize, simplify and in view of #17713 we merge the two files
complex_field.py
,complex_number.pyx
into a uniquecomplex_mpfr.pyx
.follow-up: #24489
CC: @mjungmath @fchapoton
Component: basic arithmetic
Author: Vincent Delecroix
Branch:
897416c
Reviewer: Michael Jung
Issue created by migration from https://trac.sagemath.org/ticket/24483
The text was updated successfully, but these errors were encountered: