Skip to content
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

Update autopep8 to 1.5 #279

Merged
merged 1 commit into from
Jan 31, 2020
Merged

Conversation

pyup-bot
Copy link
Contributor

This PR updates autopep8 from 1.4.4 to 1.5.

Changelog

1.5

* Support Python3.8
* Support `pyproject.toml` with `[tool.autopep8]` section.
* fix bugs
* 503, 511  : related code W503
* 489, 498 : related code E711/E712
* 449, 514 : related code W605
Links

@codecov
Copy link

codecov bot commented Jan 31, 2020

Codecov Report

Merging #279 into develop will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #279   +/-   ##
========================================
  Coverage    73.02%   73.02%           
========================================
  Files           74       74           
  Lines         2843     2843           
========================================
  Hits          2076     2076           
  Misses         767      767

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 c93b80b...0bd98d3. Read the comment docs.

@abhinavsingh abhinavsingh merged commit cc896dd into develop Jan 31, 2020
@abhinavsingh abhinavsingh deleted the pyup-update-autopep8-1.4.4-to-1.5 branch January 31, 2020 17:48
s-medvedev referenced this pull request in neonevm/proxy-model.py Oct 8, 2021
* #279 Create a separate token accounts for each ERC20 contract

* Use correct env variable in CI
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.

None yet

2 participants