App Built With Non-system Python Using Py2app In Pyenv Not Runnable On Other Machines
Solution 1:
py2app automatically defaults to --semi-standalone
mode if it thinks you are using the system interpreter. Your interpreter from Python.org shouldn't count as a "system" interpreter, but you could see what py2app
thinks using this command:
$ python -c "import py2app.build_app; print py2app.build_app.is_system()"False
One issue to watch out for: After I installed a Python.org interpreter today, bash
didn't update it's hash
cache, causing strange incompatibilities when I launched python. I had to type hash -r python
to reset the cache and make sure the correct version of python was getting used. (Another way to fix this is to log out and log in again.) I suppose it's possible that the same issue could have caused py2app
to be confused about whether or not you were using the system python.
If that doesn't do the trick, then try installing your python interpreter to a weird location, like ~/mypython
or something like that, just to make sure there's no way it can be confused for a system python.
As a last resort, I suppose you could just hack the py2app
source code so that is_system()
always returns False
. Not sure if that would have any adverse consequences, though.
PS -- Here's a little tutorial on using py2app
with a conda
-packaged application:
https://github.com/stuarteberg/helloworld Not exactly relevant to your problem here, but you could compare it with your own setup and look for any conspicuous differences.
Post a Comment for "App Built With Non-system Python Using Py2app In Pyenv Not Runnable On Other Machines"