-
Notifications
You must be signed in to change notification settings - Fork 253
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
Bug fix: windows does not have 'which' command #641
Conversation
What's the context? What's the bug, or how did this bite you? This has been working for a long while, now, I believe, so (even though I know you're right about |
This bug was found when I trying to build 'confluent-kafka-python' wheel package locally. If I run their build batch file from windows command console, it always stop at calling command 'which python'. So, I brows their code, and found this bug form 'cibuildwheel'. Also, I found other lines of code in 'windows.py' use 'where' command instead of 'which'. So, I change it, and it did work on building 'confluent-kafka-python' wheel package. And, of cause, if I run this build batch from window's git-bash, this bug no longer exist due to git for windows did have 'which' command in it. |
It is not recommended to use cibuildwheel locally on non-linux system (Linux builds use docker) as cibuildwheel install python system side.
It looks like all CI system which are tested has bash installed. |
It's interesting that we've not hit this bug before, I guess that many Windows installs have |
Nope, I agree. Just trying to understand why we haven't run into it before and why tests pass! And we're not digesting the output from |
Thanks, @MagicJack! |
Most CI Windows runners are set up to be as close to Unix as possible, even when not using bash. For example, GHA/Azure added the |
Windows does not have 'which' command, it should be 'where' command.