Remove linting error for deprecated warning #88
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ramsrivatsa
force-pushed
the
ramsrivatsak/linting-error
branch
from
01998bc
to
84a8213
Compare
ramsrivatsa
force-pushed
the
ramsrivatsak/linting-error
branch
from
84a8213
to
31591d3
Compare
|
Everything about https://discuss.python.org/t/deprecating-importlib-resources-legacy-api/11386/14?page=2 makes me sad. Why can't they just keep path. There doesn't seem to me to be a strong reason to deprecate it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Remove linting error for deprecated warning