Skip to content

Revisit getopt and optparse soft deprecations #126225

Closed as not planned
Closed as not planned
@ncoghlan

Description

@ncoghlan

Duplicate of #126180


(Based on @serhiy-storchaka's Discourse thread at https://discuss.python.org/t/getopt-and-optparse-vs-argparse/69618 ).

I'm going to draft a PR for this, and wanted an issue number for the NEWS entry.

The PR will be initially marked as DO-NOT-MERGE, as this feels like a change that needs an explicit +1 from the next SC (since we'd be reversing a deprecation that come from a previously approved PEP: https://peps.python.org/pep-0389/#deprecation-of-optparse)

Interestingly, the deprecation notice in getopt goes against the contents of PEP 389 ("The getopt module will not be deprecated. However, its documentation will be updated to point to argparse in a couple of places.")

Linked PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.13bugs and security fixes3.14bugs and security fixesdocsDocumentation in the Doc dirstdlibPython modules in the Lib dir

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions