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
Embed Python interpreter and the dependent packages with the application #146
Comments
At this point you may be better off using a Python specific packaging tool that does dependency resolution (e.g. py2app or PyInstaller). |
Using a bundled interpreter is a feature planned for the next release (5.4). |
Thank you all for replying |
I'll be able to get around to the next release early next year at the earliest. |
This can be done with 5.3 using a simple workaround. Include your Python binary in the app's "Bundled Files." Write a small wrapper shell script to open your primary script with the bundled interpreter. Select this wrapper in Platypus when you create your app. Example:
|
Thanks for replying @cylott! |
Well, you would need a static binary. My only experience is with PHP, and that one's nearly impossible to package. |
any updates on this @sveinbjornt ? |
I don't really have much time to work on Platypus at the moment, but an interim solution would be to include both the Python script and a python environment in Bundled Files, and use a shell script to run it using the python interpreter binary. |
Fixed in master. You can now specify a relative interpreter path (relative to the Resources directory of the application bundle). Just include the interpreter in Bundled Files and it should work. |
Hello,
I used Platypus on my mac to package a python based app. Which works fine on my machine where I've python 3.7.3 and all the packages are installed but it doesn't work on other Mac's where they don't have the interpreter and the dependencies.
Is there a way to package it with python interpreter and all the packages? I couldn't find anything from the documentation. Please help
Thanks
The text was updated successfully, but these errors were encountered: