Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running with "run" argument considered ambigious #1

Closed
ammaraskar opened this issue Aug 19, 2016 · 9 comments
Closed

Running with "run" argument considered ambigious #1

ammaraskar opened this issue Aug 19, 2016 · 9 comments

Comments

@ammaraskar
Copy link
Member

ammaraskar commented Aug 19, 2016

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

@vstinner
Copy link
Member

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

@zware
Copy link
Member

zware commented Aug 19, 2016

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

@zware zware closed this as completed Aug 19, 2016
@vstinner
Copy link
Member

vstinner commented Aug 19, 2016 via email

@ammaraskar
Copy link
Member Author

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

@zware
Copy link
Member

zware commented Aug 19, 2016

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

@vstinner
Copy link
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?

@ammaraskar
Copy link
Member Author

Yup, latest default.

@vstinner
Copy link
Member

Yup, latest default.

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

@vsajip
Copy link
Member

vsajip commented Aug 23, 2016

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants