> Another note about the proposal: calling it "deprecated" seems odd,
> since the proposal is really just a general-purpose callback. argparse
> isn't generating the warning, your callback function would be doing it.
> Why name it "deprecated"? How is this different than the "action"
> keyword argument that argparse already provides?
That sounds right. Maybe a better implementation would be to implement
a custom action by inheriting from argparse.Action
and do all the warning/deprecation job there.
I'll experiment with this idea on my side to see how it goes :)
Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/