Skip to content

Running with "run" argument considered ambigious #1

Closed

Description

@ammaraskar

Not sure if this belongs here but right now running bench.py with run brings up this error. It seems like there's an active issue for this: https://bugs.python.org/issue14365

> ..\python_d.exe bench.py run
usage: bench.py [-h] {run,compare,run_compare,list,list_groups} ...
bench.py: error: argument action: ambiguous choice: 'run' could match run, run_compare

As a workaround I changed my run to run_local in https://github.com/python/benchmarks/blob/master/benchmark/cli.py#L84
and
https://github.com/python/benchmarks/blob/master/benchmark/cli.py#L150
and
https://github.com/python/benchmarks/blob/master/benchmark/run.py#L445

Activity

  1. vstinner commented on Aug 19, 2016

    @vstinner
    Member

    Strange. I'm unable to reproduce the issue on Fedora 24 with Python 2.7.11 nor Python 3.5.1.

  2. zware commented on Aug 19, 2016

    @zware
    Member

    This appears to be a bug introduced in http://bugs.python.org/issue12713

  3. vstinner commented on Aug 19, 2016

    @vstinner
    Member
  4. ammaraskar commented on Aug 19, 2016

    @ammaraskar
    MemberAuthor

    Well it's an upstream issue, no need to keep it open here, right?

  5. zware commented on Aug 19, 2016

    @zware
    Member

    Because it was just introduced into 3.6 yesterday, and ought to be fixed (or reverted) very soon.

  6. vstinner commented on Aug 19, 2016

    @vstinner
    Member

    Because it was just introduced into 3.6 yesterday, and ought to be fixed
    (or reverted) very soon.

    Oh, Ammar: you compiled manually the default branch of Python on Windows?

  7. ammaraskar commented on Aug 19, 2016

    @ammaraskar
    MemberAuthor

    Yup, latest default.

  8. vstinner commented on Aug 19, 2016

    @vstinner
    Member

    Yup, latest default.

    Oh ok, fine :-) Use an older version of argparse to workaround the issue (or an older version of the repository).

  9. vsajip commented on Aug 23, 2016

    @vsajip
    Member

    That recent change to argparse which caused your breakage has now been reverted. Sorry :-(

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions