-
Notifications
You must be signed in to change notification settings - Fork 428
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
Failure to find osx-64 python.app during build test #1664
Comments
I'm not actually sure that we can have fallbacks there - that's the shebang that is saying which executable to run. I can certainly try to use pythonw on MacOS there rather than python.app, but I'm not sure exactly what the consequences of that are. I think the key issue is that we need some way of distinguishing GUI-enabled programs from CLI-only programs. If pythonw does not mess up CLI-only apps, then that is probably the best way forward. |
I thought it would be possible to check if either python.app or pythonw exist within the bin directory before writing the shebang. It is only failing on the final test in a temporary environment that is deleted straight after the test, so it doesn't have to be particularly robust. |
Both python.app and pythonw come from the same package - the python.app package. In fact, it appears that pythonw is nothing more than a link to python.app. If one is missing, I would expect both to be missing. I'm lost as to why we separate python.app and pythonw from the base python package. We don't do that on Windows. @ilanschnell can you comment on this discrepancy? |
Indeed |
I haven't had time to test the #1669 yet, but it looks as if it would work. My pythonw file contains
so it looks as if the problem is that, in post.py, the file path to python.app assumed it was in the |
Hi there, thank you for your contribution! This issue has been automatically locked because it has not had recent activity after being closed. Please open a new issue if needed. Thanks! |
I am submitting this as a new issue, although it is clearly related to #7, because this has just become a problem for my builds (https://github.com/nexpy/nexpy/blob/master/conda-recipe/meta.yaml but without commenting out the
osx_is_app
line), although they seemed to work fine a few months ago.Current conda install
The error is in running the test at the end, even though pythonw is installed in the test's bin directory.
Error message
It looks to me as if the problem is that the code in post.py (https://github.com/conda/conda-build/blob/master/conda_build/post.py) tries to run python.app, but doesn't have pythonw as a fallback option if it's not there.
The text was updated successfully, but these errors were encountered: