Release v1.6.2 building with Python 3.8 #527
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have created a
master-py2
branch to backports fixes to Python2. This PR includes:master-py2
branchmaster-py2
branchmaster-py2
branch).Release checklist (note some things don't apply in this case)
dont merge
label to all PRs that are close to be ready to merge (or merge them if they are ready) in capa and capa-rules. It doesn't apply (we are not releasingmaster
, butmaster-py2
)master-py2
until we merge this PR, but currentmaster-py2
isv1.6.1
and we know tests work.python scripts/lint.py rules/ --thorough
succeeds (onlymissing examples
offenses are allowed in the nursery). Currentmaster-py2
isv1.6.1
and we know it works.Raw diffs
linksmaster (unreleased)
sectionDocumentation
Tests
Python 3.9 doesn't support Windows 7. Build with Python 3.8 instead.