-
-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typing issue with deep_iterable validator #531
Comments
mmaslowskicc
added a commit
to mmaslowskicc/attrs
that referenced
this issue
May 24, 2019
Use bound type variables for iterables and mappings of the validated item types, so mypy does not erroneously require both the iterable attribute validated by deep_iterable and the item type validated by the first argument of deep_iterable to have the same type.
mmaslowskicc
added a commit
to mmaslowskicc/attrs
that referenced
this issue
May 24, 2019
Use bound type variables for iterables and mappings of the validated item types, so mypy does not erroneously require both the iterable attribute validated by deep_iterable and the item type validated by the first argument of deep_iterable to have the same type. Do not require optional arguments in type stubs.
10 tasks
euresti
pushed a commit
that referenced
this issue
May 27, 2019
Use bound type variables for iterables and mappings of the validated item types, so mypy does not erroneously require both the iterable attribute validated by deep_iterable and the item type validated by the first argument of deep_iterable to have the same type. This fixes #531.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run mypy check on the following code:
it results in:
mypy == 0.670, attrs == 19.1.0
The text was updated successfully, but these errors were encountered: