From: Günter M. <mi...@us...> - 2022-02-03 14:59:51
|
I am sorry for the delay and the additional work. The change turned out to be far more complicated than expected when I first proposed it. In order to have informed choices, I had to study the current state in detail first. (See [r8996] for a by-product.) I propose to start with clean up and deprecation steps to smoothe the actual OptionParser -> ArgumentParser change. (A proposal for the two first steps is attached.) Attachments: - [0001-Small-fixes-mostly-documentation-Test-more-list-settings.patch](https://sourceforge.net/p/docutils/bugs/_discuss/thread/c76f9a2618/45c6/9106/2d9c/5575/attachment/0001-Small-fixes-mostly-documentation-Test-more-list-settings.patch) (8.2 kB; text/x-patch) - [0002-Clean-up-docutilsfrontend-before-the-switch-to-arparse.patch](https://sourceforge.net/p/docutils/bugs/_discuss/thread/c76f9a2618/45c6/9106/2d9c/5575/attachment/0002-Clean-up-docutilsfrontend-before-the-switch-to-arparse.patch) (10.5 kB; text/x-patch) --- ** [bugs:#441] Move from "optparse" to "argparse".** **Status:** open **Created:** Thu Jan 06, 2022 03:02 PM UTC by Günter Milde **Last Updated:** Thu Feb 03, 2022 02:45 PM UTC **Owner:** Günter Milde The optparse documentation says: > Deprecated since version 3.2: The optparse module is deprecated and will not be developed further; development will continue with the argparse module. We are currently suppressing related deprecation warnings in the test suite. After raising the Python dependency to >=3.7, now may be the right time to make the move. --- Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |