[issue39467] Allow to deprecate CLI arguments in argparse

2020-03-03 Thread hervé
hervé added the comment: hello, First thanks everyone to took time to discute about this proposal. This topic is now opened since ~1 months so I don't think we will more feedback about this, then I will address all your comments in my changes soon to match an implementation more consensually

[issue39467] Allow to deprecate CLI arguments in argparse

2020-02-01 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: In general I agree with Raymond, although I am warmer to this feature. And I think we should have a mechanism to deprecate not only options, but subcommands. * The warnings module is used for warning about the use of API. It outputs the file and the line n

[issue39467] Allow to deprecate CLI arguments in argparse

2020-02-01 Thread hai shi
hai shi added the comment: IMHO, cli should only support atomic function.What is atomic functin? (if downstream software's feature can not keep alive without upstream fucntion, it must be an atomic function). -- nosy: +shihai1991 -4383 ___ Python

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-28 Thread hervé
hervé added the comment: 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 me

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread Raymond Hettinger
Change by Raymond Hettinger : -- Removed message: https://bugs.python.org/msg360813 ___ Python tracker ___ ___ Python-bugs-list mail

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread Raymond Hettinger
Raymond Hettinger added the comment: Will leave this open for a while so that many people can comment on the proposal before we act on it. My initial take is: * Having a way to deprecate seems useful. * In practice, I haven't seen this done very much (in big tooling such as GCC perhaps, bu

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread Raymond Hettinger
Raymond Hettinger added the comment: Will leave this open for a while so that many people can comment on the proposal before we act on it. My initial take is: * Having a way to deprecate seems useful. * In practice, I haven't seen this done very much (in big tooling such as GCC perhaps, bu

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +djarb, paul.j3, rhettinger -4383 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread hervé
Change by hervé : -- keywords: +patch pull_requests: +17585 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18208 ___ Python tracker ___ ___

[issue39467] Allow to deprecate CLI arguments in argparse

2020-01-27 Thread hervé
New submission from hervé : Today it's not possible to deprecate CLI arguments designed with argparse, it could be useful to introduce deprecation feature in argparse to allow developers to inform their apps's users when an argument is planed to be removed in the future. -- components