[Docutils-develop] [docutils:bugs] Re: #441 Move from "optparse" to "argparse".

[Günter M. <mi...@us...>]

On 2022-03-02, Adam Turner wrote:

> I've combined your changes into the attached patch, they look good to
> me as enabling works.

Thanks for look at this. We are almost there.

`python3 -W all alltests.py` came up with a buch of DeprecationMessages which
could be solved with

~~~
--- a/docutils/test/test_settings.py
+++ b/docutils/test/test_settings.py
@@ -108,8 +108,7 @@ class ConfigFileTests(unittest.TestCase):
     def setUp(self):
         warnings.filterwarnings(action='ignore',
                                 category=frontend.ConfigDeprecationWarning)
-        warnings.filterwarnings(action='ignore', module='docutils.frontend',
-                                category=PendingDeprecationWarning)
+        warnings.filterwarnings(action='ignore', category=DeprecationWarning)
         self.option_parser = frontend.OptionParser(
             components=(pep_html.Writer, rst.Parser), read_config_files=None)
~~~

Note: testing with warnings switched on is helpful. (It would also be
      good to run one or several Sphinx builds with activated warnings,
      to see whether there are uses of deprecated functions/classes.)

Now, only the entries in RELEASE-NOTES (bacwards-incompatible changes,
deprecations) and maybe HISTORY (other important changes) are missing.

...
>> I retract the suggestion to make the move now

> OK. It would be good to talk more about the "settings api" proposals. 

Yes. But this may be done in parallel to (or after) releasing 0.19b, ..., 0.19,
so that the deprecation warnings are out.


>> [...] I am increasingly convinced that settings updated from
>> configuration files are not "default settings".

> Perhaps "initital" settings?

Thats an option. Best would be to find out whether there is an precedence
of projects using both, ConfigParser and ArgumentParser, how they combine
both, and how they name partially configured settings.)



---

** [bugs:#441] Move from "optparse" to "argparse".**

**Status:** open
**Created:** Thu Jan 06, 2022 03:02 PM UTC by Günter Milde
**Last Updated:** Wed Mar 02, 2022 02:40 AM 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.