-
Notifications
You must be signed in to change notification settings - Fork 86
Use of verify_interface #464
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
Comments
Hello @reaperhulk! Thank you for reaching out to us to let us know about the deprecation of Best, |
Our CI runs you as a downstream so we actually can't remove it without breaking our own CI 😄 We'd like to remove it for the next release though! |
Are y'all currently running releases on a cadence? If not, have y'all set date for the next release? Best, |
We do not have a date set. Historically our releases happen roughly every 3 months, would suggest July/August for our next release, but we don't have a fixed release schedule. |
Hello @alex and @reaperhulk! We have removed usage of Best, |
Hi folks, I'm one of the developers of
pyca/cryptography
. We're planning to removeverify_interface
(a function we've never publicly documented and is not part of our API contract) because it no longer has any use for us, but we noticed that you have two locations you currently call it in this codebase. In both cases you should be able to substitute a type check (either check the class itself or instantiate and do anisinstance
) rather than usingverify_instance
. This will be backwards compatible to oldercryptography
and let us move forward with removal on our end.The text was updated successfully, but these errors were encountered: