Copy entrypoints that have a shebang that differs in python vs python3
#14970
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #14919 it was reported that uv's behavior differed after the first invocation. I noticed we weren't copying entrypoints after the first invocation. It turns out the shebangs were written with
.../pythonbut on a subsequent invocation thesys.executablewas.../python3so we didn't detect these as matching.This is a pretty naive fix, but it seems much easier than ensuring the entry point path exactly matches the subsequent
sys.executablewe find.I guess we should fix this in reverse too? but I think we might always prefer
python3when loading interpreters from environments.See #14790 for more background.