-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Comments
Strange. I'm unable to reproduce the issue on Fedora 24 with Python 2.7.11 nor Python 3.5.1. |
This appears to be a bug introduced in http://bugs.python.org/issue12713 |
Why do you close the issue? We should fix it or workaround it.
|
Well it's an upstream issue, no need to keep it open here, right? |
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? |
Yup, latest default. |
Oh ok, fine :-) Use an older version of argparse to workaround the issue (or an older version of the repository). |
That recent change to |
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/issue14365As a workaround I changed my
run
torun_local
in https://github.com/python/benchmarks/blob/master/benchmark/cli.py#L84and
https://github.com/python/benchmarks/blob/master/benchmark/cli.py#L150
and
https://github.com/python/benchmarks/blob/master/benchmark/run.py#L445
The text was updated successfully, but these errors were encountered: