Skip to content

4.6: Run pyupgrade without --py3-plus #5387

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

Closed
wants to merge 2 commits into from
Closed

4.6: Run pyupgrade without --py3-plus #5387

wants to merge 2 commits into from

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Jun 4, 2019

  • Target the master branch for bug fixes, documentation updates and trivial changes.
  • Target the features branch for new features and removals/deprecations.
  • Include documentation when adding new features.
  • Include new tests or update existing tests when applicable.

Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:

  • Create a new changelog file in the changelog folder, with a name like <ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.
  • Add yourself to AUTHORS in alphabetical order;

To help with backports, and related to #5275, this runs pyupgrade without --py3-plus on the 4.6-maintenance branch, to minimise the difference between it and the master branch, where pyupgrade has been run (with --py3-plus).

(And run Black.)

@codecov
Copy link

codecov bot commented Jun 4, 2019

Codecov Report

Merging #5387 into 4.6-maintenance will decrease coverage by 7.42%.
The diff coverage is 85.98%.

Impacted file tree graph

@@                 Coverage Diff                 @@
##           4.6-maintenance    #5387      +/-   ##
===================================================
- Coverage            94.28%   86.85%   -7.43%     
===================================================
  Files                  115      115              
  Lines                26362    26362              
  Branches              2603     2603              
===================================================
- Hits                 24855    22897    -1958     
- Misses                1178     3110    +1932     
- Partials               329      355      +26
Impacted Files Coverage Δ
src/_pytest/warnings.py 88.88% <0%> (ø) ⬆️
testing/test_terminal.py 93.62% <100%> (-5.29%) ⬇️
src/_pytest/_io/saferepr.py 80.43% <100%> (ø) ⬆️
src/_pytest/runner.py 96.83% <100%> (-1.19%) ⬇️
src/_pytest/main.py 91.9% <100%> (-3.94%) ⬇️
src/_pytest/debugging.py 90.25% <100%> (ø) ⬆️
testing/test_pdb.py 94.94% <100%> (-3.12%) ⬇️
src/_pytest/assertion/util.py 95.57% <100%> (-2.59%) ⬇️
src/_pytest/helpconfig.py 97.6% <100%> (ø) ⬆️
src/_pytest/reports.py 68.96% <100%> (-26.11%) ⬇️
... and 74 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 937f945...848bb16. Read the comment docs.

@hugovk
Copy link
Member Author

hugovk commented Jun 4, 2019

Ah, tests are failing, if this isn't a quick win it's probably not worth the effort.

By the way, I did test this on my fork before creating the PR, but tests all fail on forks (also for clean master and 4.6-maintenance) maybe due to the repo = pytest-dev/pytest restrictions.

Sorry for the noise, feel free to close!

@nicoddemus
Copy link
Member

I will let @asottile comment/handle this one. 😁

@asottile
Copy link
Member

asottile commented Jun 4, 2019

Yeah we can't quite do this as pytest 2.7 code isn't quite unicode clean (which is why it was running with --skip-percent-format)

@asottile
Copy link
Member

asottile commented Jun 4, 2019

Note that we're already running pyupgrade as well, just with the format fixer disabled

@asottile asottile closed this Jun 4, 2019
@hugovk hugovk deleted the 4.6-maintenance-pyupgrade-without---py3-plus branch June 4, 2019 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants