-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Fix x finding Python on Windows #104350
Fix x finding Python on Windows #104350
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
How about |
889dd34
to
f35f23f
Compare
f35f23f
to
56dfb70
Compare
Great idea, I used that instead. |
@rustbot label +A-bootstrap |
@rustbot ping |
…ebot, r=Mark-Simulacrum Add x tool to triagebot Assign the A-bootstrap label when a pr modifies the x tool. Happened in rust-lang#104350.
r? @jyn514 -- I think this seems okay but you might have the python discovery mess more in cache than I. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thanks.
FWIW I am not enthused about maintaining 4 separate entry points. I think at some point we may want to make this an even smaller shim that just invokes x.ps1 or ./x
. But that doesn't need to block this change.
@bors r+ rollup Oh, the other reason I'm not a fan of this shim is it has no upgrade path, the changes don't have an effect unless people rerun |
IMO, on Windows it's better to also try the The default installation options from |
@messense I am not willing to take large changes to the x tool at this time, unless they're to use the x.ps1 or ./x scripts. |
Fix x finding Python on Windows `x` searches through the path for `{dir}/python{2|3}?`, but this fails on Windows because the appropriate path is `{dir}/python.exe`. This PR adds the expected `.exe` extension on Windows while searching.
Fix x finding Python on Windows `x` searches through the path for `{dir}/python{2|3}?`, but this fails on Windows because the appropriate path is `{dir}/python.exe`. This PR adds the expected `.exe` extension on Windows while searching.
…iaskrgr Rollup of 11 pull requests Successful merges: - rust-lang#101967 (Move `unix_socket_abstract` feature API to `SocketAddrExt`.) - rust-lang#102470 (Stabilize const char convert) - rust-lang#104223 (Recover from function pointer types with generic parameter list) - rust-lang#104229 (Don't print full paths in overlap errors) - rust-lang#104294 (Don't ICE with inline const errors during MIR build) - rust-lang#104332 (Fixed some `_i32` notation in `maybe_uninit`’s doc) - rust-lang#104349 (fix some typos in comments) - rust-lang#104350 (Fix x finding Python on Windows) - rust-lang#104356 (interpret: make check_mplace public) - rust-lang#104364 (rustdoc: Resolve doc links in external traits having local impls) - rust-lang#104378 (Bump chalk to v0.87) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…ebot, r=Mark-Simulacrum Add x tool to triagebot Assign the A-bootstrap label when a pr modifies the x tool. Happened in rust-lang#104350.
x
searches through the path for{dir}/python{2|3}?
, but this fails on Windows because the appropriate path is{dir}/python.exe
.This PR adds the expected
.exe
extension on Windows while searching.