-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Switch to a dynamic framework. #33
Conversation
dbe0553
to
7f4d6b1
Compare
See the Briefcase PR for details on the merge strategy for this template change. There is one change (in the binary tagging workflow) that will need to be rolled back once beeware/briefcase#1934 has been merged. |
@@ -82,7 +86,7 @@ int main(int argc, char *argv[]) { | |||
} | |||
|
|||
// Set the home for the Python interpreter | |||
python_home = [NSString stringWithFormat:@"%@/support/python-stdlib", resourcePath, nil]; | |||
python_home = [NSString stringWithFormat:@"%@/Python.framework/Versions/{{ cookiecutter.python_version|py_tag }}", frameworksPath, nil]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Python.framework/Versions/{{ cookiecutter.python_version|py_tag }}
appears 3 times in this function, and {{ cookiecutter.python_version|py_tag }}
appears 5 times. Can we factor them out into variables?
App template changes to support the use of a dynamically loaded Python.framework.
Refs beeware/Python-Apple-support#191
Also drops Python 3.8 support, and adds Python 3.13 support.
Briefcase-Repo: https://github.com/freakboy3742/briefcase.git
Briefcase-Ref: version-bumps
PR Checklist: