Replies: 7 comments 6 replies
-
Thank you for the report. I will investigate if I can fix this error for |
Beta Was this translation helpful? Give feedback.
-
Fixed in |
Beta Was this translation helpful? Give feedback.
-
@sodul please let me know if the new version works for you. Feel free to close the discussion if it does, or report any issues you encountered. |
Beta Was this translation helpful? Give feedback.
-
For reference these are relevant issues in mypy: |
Beta Was this translation helpful? Give feedback.
-
I am working on a PEP for this kind of situation; input would be greatly appreciated. Current PEP proposal: https://peps.python.org/pep-0705/ |
Beta Was this translation helpful? Give feedback.
-
@alicederyn Thank you! I would be happy to help. |
Beta Was this translation helpful? Give feedback.
-
@vemel FYI mypy has improved the issue in the 0.981 release python/mypy#13311 |
Beta Was this translation helpful? Give feedback.
-
After upgrading to boto3 1.28 from 1.26 we noticed that some output types have become incompatible as input types, raising mypy errors.
For example:
If you look at the type annotation I would assume that they should be compatible:
But somehow you can't use a
IpRangeOutputTypeDef
as input for aIpRangeTypeDef
which is less strict. All the keys being the same with the only difference being that ``IpRangeTypeDefhas
total=False` which is less strict.I'm not sure if this should be filed as a bug or if we are suppose to handle these things differently so I posted it under Discussions.
Beta Was this translation helpful? Give feedback.
All reactions