DEPR: iterkv change Deprecation to FutureWarning #10867
Merged
+8
−8
Conversation
This file contains hidden or 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
Contributor
|
what exactly is the difference between a |
Member
Author
|
DeprecationWarning is not visible to users (by default), FutureWarning is That is the reason we use mostly FutureWarnings |
Contributor
|
oh ok, good to know. |
Member
Author
|
Problem is that you actually want a combination of both: only show the warning if you call the function/method triggering it, and not when a library that you are using calls such a method. But AFAIK that is not possible. |
jorisvandenbossche
added a commit
that referenced
this pull request
Aug 21, 2015
DEPR: iterkv change Deprecation to FutureWarning
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
So this is visible to the users (already long time deprecated in the docs)