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
pyflakes cleanup of elliptic curves #25463
Comments
Branch: public/25463 |
Commit: |
New commits:
|
comment:2
I will look at this, and with luck will finish it off. Thanks for doing the bulk so far. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
OK so I positively review all the changes made in the first commit, and offer more, which almost finishes off sage.schemes.elliptic_curves. Remaining issues:
|
comment:5
I think we should already do the changes here, and maybe care for the few remaining ones later in another ticket. There is no need to do anything for all.py. I agree with your changes, and propose to set to positive once a patchbot is green. |
comment:6
There are failing doctests in sage -t src/sage/schemes/elliptic_curves/BSD.py These 3 failing doctests seem to be improvements over the existing ones. Should we just change them ? |
comment:7
Yes, it seems that fixing the typo on current line means that the 5-part of the proof now goes through. I would like Chris Wuthrich to give a view on both this and the one in padic_lseries before we merge this, but I will make an updated commit now. I guess this will be the first time in history where pyflakes has succeeded in solving one of the Millennium $1M Prize problems! |
Reviewer: John Cremona, Frédéric Chapoton |
Changed author from Frédéric Chapoton to Frédéric Chapoton, John Cremona |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
I guess I will have to learn what pyflakes is. By now I assume it is a thing that picks up redundant or bad lines. Tell me if I need more. (Is there a version for cython, too? The amount of cython warnings during compilation should frighten anyone.)
Yes, they are, please delete. Yes, the crit(e)_lw is mine. Sorry about this and thanks for correcting. I agree that the doctest can be changed as proposed. Let me know if I need to look at anything further, I am happy to help. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Thanks -- all the last commit does is delete the lines which had been commented out. Yes, pyflakes does a syntax check & warns of unused imports, of variables assigned to but never then used (which can be a bug, as with one of these), or re-use of a variable name. I don't know about cython. |
comment:13
I have just launched my patchbot. We can give a positive review once it's green. |
comment:14
green bot. Thanks ! |
Changed branch from public/25463 to |
Aim: that all files in src.sage.schemes.elliptic_curves pass pyflakes, except for all.py.
CC: @categorie
Component: elliptic curves
Author: Frédéric Chapoton, John Cremona
Branch/Commit:
70a2fc2
Reviewer: John Cremona, Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/25463
The text was updated successfully, but these errors were encountered: