-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Make sure conda does not use polyglot shebangs #12043
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
Conversation
Review build status
Once it's done, use this command to try it out in a new conda environment:
|
Ready for review but I want to check the canaries that come out of this PR once #12047 is addressed. |
Are canaries online again? :D |
I asked about the canaries because I wanted to review how the entry points were being rendered 😬 |
conda-build 3.23.0 is on defaults now, we'll get the canary builds on the main branch shortly |
Awesome, the test changes in the recipe should reveal the shebangs properly. So we just need to check the logs. |
Description
Minimum work to fix #11885 and close #11893.
More robust solution long-term available at #11995.
Basically we prevent
conda
from using the polyglot shebang approach with two checks:$PREFIX
, we are most probably packagingconda
. Do nothing and let prefix replacement handle that at install time (replace_long_shebang()
right above our function)conda init --install
outside conda-build (there's no reason to, but 🤷), we ensure they end up with a#!/usr/bin/env python
shebang by calling the function with a new flag.Checklist - did you ...
news
directory (using the template) for the next release's release notes?