Add warning filters for upstream pkg_resources
warnings
#4127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In #4124, we attempted to address
pkg_resources
API usage DeprecationWarnings by removing all usage ofpkg_resources
from SCT. As it turns out, though, SCT wasn't the only source of these warnings.Instead, the call-specific warnings are from upstream packages. (There are open issues for solving these warnings in their respective packages (matplotlib, google_auth), see: #4123 (comment))
So, the best we can do is filter these warnings while we wait. (This is the option chosen by many projects, see: https://github.com/search?q=ignore%3ADeprecated+call&type=code)
Linked issues
Fixes #4123