-
Notifications
You must be signed in to change notification settings - Fork 41
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
Resolve ResouceWarning and DeprecationWarning messages for 3.11 #212
Comments
Thanks for this report as well. The socket leak looks like the same one in #211, but I'll use this issue to handle the separate deprecation warnings for |
Looks like the |
I think based on python/cpython#93610 they were marked as deprecated, but you might want to follow up there. |
I'll tackle this today. |
Hmm, I don't think there's much we can do about these Removing the "bug" label for now, since these are not replaceable in our currently supported versions. |
I do maintain importlib_resources to enable access to |
Thanks @jaraco! Yeah, I'm in favor of moving away from these APIs if there's a high-quality shim we can use, which |
Resolve ResouceWarning and DeprecationWarning messages for 3.11
This example presents ResourceWarning and DeprecationWarning messages that appear to be from sigstore sources (and other source, which are out of scope).
Version
The text was updated successfully, but these errors were encountered: