-
-
Notifications
You must be signed in to change notification settings - Fork 541
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
{Real,Complex}Ball: Miscellaneous fixes and improvements #19152
Comments
Commit: |
Branch: u/mmezzarobba/19152-arb-misc |
Last 10 new commits:
|
Dependencies: #19063 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:7
Rebased and extended. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:10
As discussed in #17220, the |
Changed branch from u/mmezzarobba/19152-arb-misc to u/cheuberg/19152-arb-misc |
Reviewer: Clemens Heuberger |
comment:12
I read the modifications and have the following comments.
New commits:
|
comment:59
Replying to @mezzarobba:
Is there a particular reason for not using Apart from that question, all my concerns have been dealt with and as far as I can see, Jeroen's comments are also all taken into account. I think that #19568 is not too related to the changes in this ticket ( Therefore, I intend to set this ticket to positive as soon as the question about lazy imports is settled. |
comment:62
Replying to @cheuberg:
Yes: I'm not sure that the modules are expensive enough to be worth importing with |
comment:63
Replying to @mezzarobba:
Can you at least push your attempt such that it can be investigated? |
comment:64
Replying to @jdemeyer:
The following change:
leads to:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:67
Replying to @mezzarobba:
I cannot reproduce this. I used your diff and had no problems with Let's see what the patchbots say. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:69
So the patchbot could reproduce the problem (and in the meantime, I could also reproduce it). Thus I reset the branch to the earlier commit. The commit with the lazy import is still available as branch My intention now is to set this ticket to positive review as it is in the next few days unless somebody objects. |
comment:70
Fine with me; There seems to be something fishy with lazy import and coercion. Can you open a new ticket and push your lazy-import branch there? |
comment:72
I just noticed a stupid bug in the new |
comment:73
It's safer to do it in a new ticket (The release manager might already have pulled this ticket for inclusion). |
Changed branch from public/19152-arb-misc to |
Mostly for compatibility with RIF/CIF.
Depends on #19063
CC: @cheuberg
Component: numerical
Author: Marc Mezzarobba
Branch/Commit:
0a04e62
Reviewer: Clemens Heuberger
Issue created by migration from https://trac.sagemath.org/ticket/19152
The text was updated successfully, but these errors were encountered: