-
Notifications
You must be signed in to change notification settings - Fork 12
Description
I ran:
cargo install --force unfuckAnd get the following:
error: failed to run custom build command for python27-sys v0.5.2
Caused by:
process didn't exit successfully: C:\Users\Owner\AppData\Local\Temp\cargo-installjv6TdT\release\build\python27-sys-3402b30bc412a50e\build-script-build (exit code: 101)
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: "No python interpreter found of version 2.7"', C:\Users\Owner.cargo\registry\src\github.com-1ecc6299db9ec823\python27-sys-0.5.2\build.rs:453:65
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile unfuck v0.3.0, intermediate artifacts can be found at
Does Python 2.7 need to be in your path even to install it through cargo? I saw that listed in the building section, but wasn't sure if you needed it simply to install it too.
In addition, does it matter how its added to your path? For example, I have Python 3.7, 3.8, 3.9, and 3.10 installed currently. I call 3.10 with just Python, but 3.9 with python3.9. Would having Python 2.7 added to my path as python2.7 mess up the functionality?