John Hagen added the comment:
Is there any consensus on how to move forward with this? I feel there are at
least 4 options:
1) Do nothing.
Pro: No work.
Con: It feels misleading to the user since the docs clearly state it's
deprecated. Some users (especially new ones) may miss the fact they should
really be using argparse.
2) Throw PendingDeprecationWarning from optparse, and simply suppress it where
it's used.
Pro: Not as much work. Users of optparse are properly notified.
Con: Kicks the can down the road for someone else to have to eventually
port off of optparse.
3) Throw PendingDeprecationWarning from optparse and port stdlib modules to
argparse.
Pro: Seems like the "purest" solution at least from what is indicated in
docs that it will no longer be supported. Users of optparse are properly
notified.
Con: Most amount of work. argparse has some bugs that need to be patched.
4) Some combination of 2) and 3) where some modules are suppressed and others
are ported.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue25521>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
