-
-
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
Python 3 preparation: Change some code to use more modern Python idioms #15984
Comments
Branch: u/wluebbe/ticket/15984 |
comment:1
New commits:
|
Commit: |
comment:3
Rebased on 6.2.beta6 and resolved merge conflicts. |
comment:4
And the test report:
|
comment:5
I think it would also be good to change |
comment:6
There are 151 modules (py and pyx combined) which have at least one of The change makes sense as (by far) most modules use But as this change is already pretty large I would prefer to see this change in a separate ticket/branch. |
comment:7
I think it fits well with this ticket (plus how many of those modules overlap with this one?). Also one large sweeping change is the same to me as two large sweeping changes (especially with different commits), but with the added benefit of an only one time potential rebase. If you still disagree and want it in a separate ticket, then you can set this to positive review. |
Reviewer: Travis Scrimshaw |
comment:8
I generated 151 patched py and pyx files. 3 pyx files gave doctest failures. And I got merge conflicts with this branch. Therefor I set this ticket to "positive review" (as suggested above). I will open a separate ticket for |
Author: Wilfried Luebbe |
Changed branch from u/wluebbe/ticket/15984 to |
This fixer changes code like
type(x) == T)
andwhile 1:
and it introduces thesorted()
function where appropriate.These changes are optional, but they improve style and may provide a small performance gain.
Changes according to
lib2to3/fixes/fix_idioms.py
:Component: distribution
Author: Wilfried Luebbe
Branch/Commit:
6964533
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/15984
The text was updated successfully, but these errors were encountered: