This repository was archived by the owner on Jun 16, 2026. It is now read-only.
Support typeguard 3.x and 4.x - #392
Merged
Merged
Conversation
typeguard 3.0 changed the signature of `check_type` (dropped the leading `argname` argument) and replaced the raised `TypeError` with a new `TypeCheckError` class that is not a subclass of `TypeError`. Update the `check_type` call and exception handler accordingly, and bump the pin from `>=2.5.1,<3.0.0` to `>=3.0`. Verified against typeguard 3.0.2 and 4.5.2. All tests pass on both. Also unblocks downstream consumers (e.g. larq-zoo) that were stuck on typeguard <3 transitively. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Tombana
approved these changes
May 19, 2026
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
typeguard 3.0 changed the signature of
check_type(dropped the leadingargnameargument) and replaced the raisedTypeErrorwith a newTypeCheckErrorclass that is not a subclass ofTypeError. Update thecheck_typecall and exception handler accordingly, and bump the pin from>=2.5.1,<3.0.0to>=3.0.Verified against typeguard 3.0.2 and 4.5.2. All tests pass on both. Also unblocks downstream consumers (e.g. larq-zoo) that were stuck on typeguard <3 transitively.