From: Adam T. <aa-...@us...> - 2022-01-12 16:16:37
|
Sorry for the radio silence! I've made some progress in this branch ( https://github.com/AA-Turner/docutils/tree/argparse ) -- currently fixing the last few failing tests and then will clean up the commit history and propose as a patch. The work does lead me to ask about how pace of deprecations / removal (partly to help my chances of getting the patch accepted, and partly for 'nicer' code). Can I remove the "old" config parsing logic? It was deprecated in 2003 in R1643 ( https://sourceforge.net/p/docutils/code/1643/ ). Equally, when deprecating features that would be obsoleted by my changes, would you suggest announcing removal in v0.20.0, v1.0.0, etc? (I have seen the proposed deprecation policy -- my personal feedback would be that it should go along with a versioning policy. Python itself is special in that they can't really bump the major version. If Docutils adopted semantic versioning, then removals would simply trigger a major version bump -- we could add additional language on at least X minor releases with deprecations before removal, for example). A --- ** [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 Jan 06, 2022 03:16 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. |