Deprecate 3.6 and add 3.11 #117
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
@HunterMcGushion This is a small maintenance one :-) With 3.11 quickly approaching, however, it's good to have PRs tested on it. I will manually upgrade from the |
HunterMcGushion
approved these changes
Aug 31, 2022
Owner
HunterMcGushion
left a comment
HunterMcGushion
left a comment
There was a problem hiding this comment.
Looks good, @MiWeiss. Thank you.
MiWeiss
added a commit
to MiWeiss/docstr_coverage
that referenced
this pull request
Sep 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Required for test environment upgrades (#108, #111).
Python 3.6 reached EOL, and users still relying on it can continue to use docstr_coverage v2.2.