-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
port cli to clap 4.0 #4445
base: main
Are you sure you want to change the base?
port cli to clap 4.0 #4445
Conversation
Similar in spirit to #3512 |
I believe you can use the following command to test your changes locally: # this runs all of the tests (not necessary if you know which test is affected)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v
# this runs only the test suite named "test_whatever" (usually located at `Lib/test/test_whatever.py`)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v test_whatever For a list of all resources and more command-line options, you can execute |
Looks like allow_hyphen_values on |
That WASI failure seems to be unrelated. |
If you aren't able to figure out why Related: clap-rs/clap#3903 |
Ok. How can I run only this one test? |
I believe you can use the following command to test your changes locally: # this runs all of the tests (not necessary if you know which test is affected)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v
# this runs only the test suite named "test_quopri" (located at `Lib/test/test_quopri.py`)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v test_quopri For a list of all resources and more command-line options, you can execute |
clap 4.1 is also out recently |
Any updates on this? is it going to be merged soon or shall i make a PR based on this one? |
Please, make a new one. I'll close this PR in favor of yours. |
No description provided.