This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author 4383
Recipients 4383, djarb, paul.j3, rhettinger
Date 2020-01-28.10:31:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580207513.47.0.554519949479.issue39467@roundup.psfhosted.org>
In-reply-to
Content
First, thanks Raymond for your worth useful comment.

* Concerning the usage of the warning module what do you suggest to use then?  To use "print"? 

* Concerning "hook or flag" and the 3 new params in my PR, I think developers would appreciate to give a customized message to their users to inform that something will be removed for X reasons in the X release. The "pending" notion could be removed to keep the API lightweight, but with a well documented feature I don't seen terrible thing to understand here, maybe we need to put more effort on documentation and example (related to my changes).

* Concerning the fact to move deprecation management outside the declaration of the argument, I think it could be misleading to deprecate something in another place in the code, in other words it could introduce some more difficulties to understand the code. If the deprecation is declared in the argument declaration then all the info are centralized in one place and the parser know what to do in this situation.

Thoughts?
History
Date User Action Args
2020-01-28 10:31:534383setrecipients: + 4383, rhettinger, djarb, paul.j3
2020-01-28 10:31:534383setmessageid: <1580207513.47.0.554519949479.issue39467@roundup.psfhosted.org>
2020-01-28 10:31:534383linkissue39467 messages
2020-01-28 10:31:534383create