You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading to 1.34.92 (confirmed with 1.34.93) our codebase is getting 2 new mypy errors with:
InventoryConfigurationOutputTypeDef vs InventoryConfigurationTypeDef
LifecycleRuleOutputTypeDef vs LifecycleRuleTypeDef
To Reproduce
Steps to reproduce the behavior:
Add code that works with the output as input.
InventoryConfigurationOutputTypeDef, LifecycleRuleOutputTypeDef
> mypy s3.py
s3.py:18: error: Argument 1 to "append" of "list" has incompatible type "LifecycleRuleTypeDef"; expected "LifecycleRuleOutputTypeDef" [arg-type]
Found 1 error in 1 file (checked 1 source file)
Expected output
no error
Additional context
Your OS macOS and linux, boto3-stubs installation method, boto3 version, etc.
Incompatible types (expression has type "list[LifecycleRuleOutputTypeDef]", TypedDict item "Rules" has type "Sequence[LifecycleRuleTypeDef]") [typeddict-item] (1,955:64)
As far as I understand, before you used mypy-boto3-s3 1.34.65. There was a bug fixed in #244 that incompatible output shapes were used instead of separating output and input shapes in case of conflict.
For this particular shape input and output definitions are not compatible. So, type: ignore looks like the easiest solution.
Describe the bug
After upgrading to 1.34.92 (confirmed with 1.34.93) our codebase is getting 2 new mypy errors with:
InventoryConfigurationOutputTypeDef
vsInventoryConfigurationTypeDef
LifecycleRuleOutputTypeDef
vsLifecycleRuleTypeDef
To Reproduce
Steps to reproduce the behavior:
Add code that works with the output as input.
InventoryConfigurationOutputTypeDef, LifecycleRuleOutputTypeDef
boto3-stubs[s3]
mypy
/pyright
on the following code sampleActual output
Expected output
no error
Additional context
Your OS macOS and linux,
boto3-stubs
installation method,boto3
version, etc.Relates to #208
The text was updated successfully, but these errors were encountered: