-
Notifications
You must be signed in to change notification settings - Fork 24
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
build improvements #109
build improvements #109
Conversation
tox.ini
Outdated
exclude = .git,__pycache__,docs/source/conf.py,old,build,dist | ||
max-line-length = 90 | ||
exclude = .git,__pycache__,docs/source/conf.py,old,build,dist,.venv,.tox,.idea | ||
max-line-length = 120 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regardless of the value here, black
defaults to 88
, so they suggest setting the flake8 config to 88: https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering about that -- black wasn't giving an error but flake8 was on those lines. I've updated the flake8 config per the black documentation.
Codecov Report
@@ Coverage Diff @@
## master #109 +/- ##
==========================================
+ Coverage 96.27% 96.82% +0.55%
==========================================
Files 20 20
Lines 483 473 -10
==========================================
- Hits 465 458 -7
+ Misses 18 15 -3
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
.pre-commit-config.yaml
Outdated
# - repo: https://github.com/pre-commit/mirrors-mypy | ||
# rev: v0.931 | ||
# hooks: | ||
# - id: mypy | ||
# exclude: ^tests/ | ||
# args: [--strict] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this meant to be commented out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to disregard: just saw that this has an answer in the PR description
c0d05f7
to
9f16800
Compare
For some reason |
bfe9909
to
cfd6140
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build changes look good to me, although there are other breaking changes sprinkled through the PR (like removing of Link.__iter__
) and several others which means we will have to release as a new major version.
I think I would like to separate the build improvements from the functionality change to isolate the breaking code changes in a different PR.
Yeah, I think you make a totally valid point. A bit of context on the breaking changes: the shift from |
After further discussion, it looks like the most sensible move might be to accept this PR after cutting a minor release. This will avoid the complexities of getting this PR's non-breaking bits in without the breaking portions. |
Numerous build improvements: