-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Python3 doesn't work on Android #484
Comments
I do not know if this is related but hostpython3 does not seem to work properly hostpython2
hostpython3
|
This is expected, the python.host binary is in the arm-python folder, so I guess the hostpython should work correctly if run from On 03/11/15 14:12, Nicolas wrote:
|
Actually, it's an interesting observation that the hostpython2 will run from the arm-python dir but hostpython3 won't, but I think this is probably just some difference between py2 and py3 (it's not impossible it could be important though). I've actually narrowed down the first failure of python3 on android to the calculate_path function in which python finds its prefix and exec_prefix internal variables. Since it runs this far, I don't think the main issue can be a hostpython problem, but I'll keep it in mind - thanks! |
Thank you for your explanations and the test result.
|
I've got it working using the new python for android builds from CrystaX, though cross compiling cython etc is still a bit of a pain, and it'll need some thought to integrate this new method into the p4a build process. |
it finally works! https://github.com/kivy/python-for-android/tree/python3_support |
Added by #546. |
I'm posting this issue so that anyone looking can see the current state of things.
Right now, p4a has a python3 recipe using some sl4a patches for python 3.4. These allow it to compile, but python crashes during Py_Initialize on the device. The reason could be some problem with these patches, or something in our extra patches to change how libs are loaded (I haven't tried without these, this might be worth looking at).
I'm currently investigating this by starting to redirect python's internal logging to logcat (as this crash happens before we can do this globally for python-level logs). Another option would be to use remote gdb, but this is fiddly.
Any input or testing from others is welcome here - I don't really know what's wrong, and don't have a lot of ideas for how to continue.
The text was updated successfully, but these errors were encountered: