fix: restrict typeguard version for NamedTuple compatibility #199
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
Codecov Report
@@ Coverage Diff @@
## master #199 +/- ##
=======================================
Coverage 98.19% 98.19%
=======================================
Files 15 15
Lines 1665 1665
Branches 265 265
=======================================
Hits 1635 1635
Misses 28 28
Partials 2 2 Continue to review full report at Codecov.
|
alexander-held
force-pushed
the
fix/typeguard-namedtuple
branch
from
02f54ce
to
99da0b2
Compare
This was referenced Jun 7, 2021
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.
The recent
typeguardreleases2.11.0and2.11.1cause errors in tests when type checking classes inheriting fromtyping.NamedTuplein Python 3.7 (and 3.6), as reported in agronholm/typeguard#175. This restricts the version to2.10.0and below as a temporary fix.