Skip to content
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

NoExecutableFound should write to stderr and return non-zero #9

Closed
uranusjr opened this issue Apr 14, 2020 · 3 comments
Closed

NoExecutableFound should write to stderr and return non-zero #9

uranusjr opened this issue Apr 14, 2020 · 3 comments
Milestone

Comments

@uranusjr
Copy link

I was trying to use something like py -X.Y -c "import sys; print(sys.executable, end='')" to detect the location of a given interpreter, but the execution result for a non-existant interpreter makes it difficult to handle the output. It would be much easier if the launcher fails in a more script-friendly way.

@brettcannon
Copy link
Owner

Yep, hence why both issues are listed in the TODO required to reach an MVP. 😉

brettcannon added a commit that referenced this issue Apr 18, 2020
@brettcannon
Copy link
Owner

OK, everything that was writing to stdout on failure should now be writing to stderr and there is a non-zero exit code as well. Let me know if it works for you!

@uranusjr
Copy link
Author

It works flawlessly 🎉

@brettcannon brettcannon added this to the MVP milestone Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants