-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add FutureWarning to deprecated_call
#11448
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
Add FutureWarning to deprecated_call
#11448
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As futurewarning doesn't relate to deprecation,its wrong to add it there
|
@RonnyPfannschmidt I've mentioned this over in #11447 already, but the Python docs clearly disagree with you:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changing back to comment after reading up on the details probided by @The-Compiler
|
@The-Compiler after crosschecking the documentation text used, i`m under the strong impression that
the documentation text is the linked library is clearly targeted at programmers and to my understanding it is using the wrong warning type here IMHO we should not mix user facing warnings and programmer facing warnings without a way to control the choice |
|
People test end-user facing applications with pytest (that's my primary usage of pytest, FWIW). We do already have a way to control which warning is emitted if you want to be specific:
|
|
thank you for elaborating, consider me convinced |
|
Thanks a lot everyone for the discussion and @chrimaho for the contribution! |
FutureWarningtodeprecated_call()#11447changelogfolder.AUTHORSin alphabetical order.Close #11447