Update Python path in processors to reflect changes in macOS 12.3+ #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of macOS Monterey 12.3, the version of Python 2 that shipped with macOS located at
/usr/bin/pythonhas been removed. More context can be found in some posts from Mac admins at the beginning of 2022, aggregated here.Since version 2.0.2, AutoPkg's installer has included its own Python 3 framework, symlinked from
/usr/local/autopkg/python. This pull request adjusts the "shebang" interpreter paths of processors to replace/usr/bin/env pythonwith the AutoPkg Python 3 path.NOTE: Because AutoPkg processors are imported as modules by AutoPkg and not executed directly, processors' shebang has no effect in normal usage. However: (a) some people execute processors directly during testing, and these tests won't work unless the shebang points to a valid Python 3, and (b) having instances of
/usr/bin/env pythonin the codebase could lead to confusion for people not deeply familiar with processor behavior.Thank you for your consideration!