Modernize codebase to python 3.7+ standard#2480
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2480 +/- ##
==========================================
+ Coverage 97.99% 98.85% +0.86%
==========================================
Files 118 118
Lines 16222 16222
Branches 3143 3143
==========================================
+ Hits 15896 16037 +141
+ Misses 264 131 -133
+ Partials 62 54 -8
|
|
I'm in favour of merging this because I like blank lines and double quotes, but I'm not sure if the higher-ups will like it. |
|
@Fuyukai My thinking is that you are already using |
|
I hope this can be merged. I'm realizing that it might seem daunting to review this, given the diff size, but the tools I've used are conservative w.r.t modifying behavior, so the changes should be relatively safe. |
|
@Fuyukai as a member, you get to approve and merge this if you like it! |
|
I hope it can be merged. I want to make further changes on top of this. |
pquentin
left a comment
There was a problem hiding this comment.
Thanks! Can you please exclude notes-to-self?
@pquentin I've done so now. I get one failing test suite, but I think it might be a case of test flakiness? What is your take? |
|
Not sure what's going on sorry. I've relaunched the Ubuntu 3.7 tests a few times and it appears to fail consistently which is concerning. |
I'll see if I can figure out what is going on. Perhaps later today. |
|
I can confirm that the Ubuntu 3.7 failures are not specific to this pull request. |
Thanks @pquentin! Was scratching my head over this one. |
|
Would you mind opening a pull request that skips this test on Ubuntu and Python 3.7 specifically? I can only imagine that a fix in more recent versions was not backported there. I don't want to invest time in debugging this, especially when Python 3.7 won't be supported anymore in 7 months, and this is blocking us. |
|
Looks like this one is finally good to go! Thank you so much for all the help @pquentin! |
|
(I'll let you click on the green merge button yourself!) |
This PR is the result of a one-off run of
pyupgradeon the trio code base.For future reference, this was done by running the following command from the project root:
I also ran black in preview mode (
black --preview), which mainly results in string cleanup.