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
First of all, thanks for maintaining all of these type hints! They've saved me from many bugs.
I noticed that types-pyOpenSSL depends on types-cryptography, despite types-cryptography being marked as obsolete (due to the upstream repository maintaining its own type stubs).
This causes false positives when typechecking a codebase that uses both pyOpenSSL and cryptography, as checking the former pulls in types-cryptography, which then conflicts with the correct baked-in types.
I think the fix here is to just remove the types-cryptography dependency, since it should no longer be strictly necessary. If that sounds alright, I'm happy to do a quick PR to do that.
The text was updated successfully, but these errors were encountered:
Due to limitations with our build and test system, type packages can't depend on non-type packages at the moment. This is tracked in #5768 and #5618. I'm closing this as a duplicate here as we will update all dependencies when able to do so.
First of all, thanks for maintaining all of these type hints! They've saved me from many bugs.
I noticed that
types-pyOpenSSL
depends ontypes-cryptography
, despitetypes-cryptography
being marked as obsolete (due to the upstream repository maintaining its own type stubs).This causes false positives when typechecking a codebase that uses both
pyOpenSSL
andcryptography
, as checking the former pulls intypes-cryptography
, which then conflicts with the correct baked-in types.I think the fix here is to just remove the
types-cryptography
dependency, since it should no longer be strictly necessary. If that sounds alright, I'm happy to do a quick PR to do that.The text was updated successfully, but these errors were encountered: