Strict typing, py.typed and link issues #8
Merged
Conversation
This file contains 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
Avasam
force-pushed
the
Strict-typing-and-py.typed
branch
5 times, most recently
from
804adb5 to
62b2483
Compare
Closed
Avasam
force-pushed
the
Strict-typing-and-py.typed
branch
from
62b2483 to
b418eb9
Compare
|
Looks like coverage was already missing. Not caused by this PR. |
Avasam
force-pushed
the
Strict-typing-and-py.typed
branch
from
b418eb9 to
81a4e4c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ref: jaraco/skeleton#143
Closes #7
Works towards pypa/setuptools#2345
Upstream issues:
Another one that could reasonably use strict type-checking immediately.