Skip to content

configure.py: upgrade from optparse to argparse #29813

Description

@cclauss

Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.

Describe the solution you'd like
Please describe the desired behavior.
optparse is deprecated in favor of argparse so configure.py should be upgraded to use the newer module. This could be cherrypicked from #26725 without taking the unrelated changes in that PR.

Describe alternatives you've considered
Please describe alternative solutions or features you have considered.
Leaving the code the way it is because the current DRAFT Python 3.9 docs still show support for the deprecated module.

Activity

  1. added
    pythonPRs and issues that require attention from people who are familiar with Python.
    on Oct 2, 2019
  2. vccolombo commented on Oct 2, 2019

    @vccolombo

    Hello! I would love to try this one. Already taking a look on what I can do.

  3. sam-github commented on Oct 2, 2019

    @sam-github
    Contributor

    Sounds reasonable to me. For the reader, argparse also exists in 2.7: https://docs.python.org/2.7/library/argparse.html

  4. cclauss commented on Oct 2, 2019

    @cclauss
    ContributorAuthor

    @vccolombo Please don't start from scratch... Start with the code in #26725

  5. vccolombo commented on Oct 2, 2019

    @vccolombo

    @vccolombo Please don't start from scratch... Start with the code in #26725

    Hey, I opened a PR, but I could use some help there. Thank you very much

  6. KuthorX commented on May 28, 2020

    @KuthorX
    Contributor

    It seems this was solved, but the code didn't be merged? Should this issue be closed?

  7. cclauss commented on May 28, 2020

    @cclauss
    ContributorAuthor

    Let's leave it open. The code did not get merged so the issue remains valid.

  8. RaisinTen commented on Oct 17, 2020

    @RaisinTen
    Member

    Hello @cclauss. May I work on this issue please? 🙂

  9. cclauss commented on Oct 17, 2020

    @cclauss
    ContributorAuthor

    YES. You do not have to ask for permission. Your PR needs to have some tests too. If you see something that needs fixing then please open a PR. If multiple people open a PR to fix the same issue then it is almost always a learning opportunity.

  10. RaisinTen commented on Oct 17, 2020

    @RaisinTen
    Member

    @cclaus I was wondering whether I should start with the code from #26725 or #29814. The author of the second one probably added his changes to the code mentioned in the first PR but he also mentions that the PR fails in the PR description. Also, do I simply start off by copying the code and make it work or am I supposed to fetch the commits from the PR branch, add my commits and make a PR here?

  11. cclauss commented on Oct 17, 2020

    @cclauss
    ContributorAuthor

    My suggestion would be that you start a brand new PR and cherrypick things that you like from the other two. Make sure that you put closes #26725, #29813, #29814 at the top of your PR (even if they are already closed) so that reviewers can quickly find details of previous attempts. Thanks for doing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    pythonPRs and issues that require attention from people who are familiar with Python.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions