@chrysn commented on May 2, 2018, 10:09 PM UTC:
The Android launcher for Kivy, as available for download as an APK, currently ships with Python 2.7.
Please consider building a Python 3 version in parallel (or shipping both interpreters and selecting the Python version in android.txt) so that current programs can be tested and developed in this environment as well. (Personally, my interest in working with it starts when #5241 is merged -- that's a feature that only makes sense to use with Python 3, ideally 3.6 or later.)
This issue was moved by tshirtman from kivy/kivy/issues/5724.
welcome[bot] commented on May 2, 2018, 10:09 PM UTC:
@tshirtman commented on May 6, 2018, 3:44 PM UTC:
That's probably more relevant on the python-for-android project, since that's where the launcher code is.
@chrysn commented on May 6, 2018, 4:22 PM UTC:
@gottadiveintopython commented on May 13, 2018, 3:44 AM UTC:
Have you tried new Kivy-Launcher?
It have some bugs but worked for me.
@chrysn commented on May 13, 2018, 6:06 AM UTC:
@kuzeyron commented on May 13, 2018, 6:21 AM UTC:
Security reasons it's always better to compile the apps yourself than running code that isn't inspected.
If you need help with the compiling. Feel free to join #kivy on IRC/FreeNode.
Edit: I forgot to point out a few things. To install it from other sources than Google Play is where the Security lacks.
@kuzeyron, I appreciate your concern, but there is a Python 2 kivy launcher on on kivy.org, so the same argument should go for either Python version.
I do value having a launcher available in built form (don't partiularly care for Google's playstore as F-Droid is the package manager I use). To me the main purpose of the launcher is to allow people to try whether their use cases can work with python-on-android (which I currently can't as I develop on 3), and for that I rather install a clearly licensed APK downloaded from the Kivy project on a testing Android device w/o any security relevance than installing gigabytes of mixed licensed Android NDK+SDK from Google onto my development machine.
Yes I know about the launcher. My point was to note that you shouldn't use from sources you don't know.
I should have clarified that a little bit better. Thanks for noting me that :)
I'm not sure what is the official status of the new launcher, but there should be no major barrier to having a python 3 version. Mostly, nobody has got around to creating and testing an official version yet. I'll try to make sure to include this as part of the next release.
Hi,
Thanks all for the great work. A few weeks into kivy only, so bear in mind....
After struggling a bit trying to test video on kivy I realized the actual launcher is on 1.09 and pygame backend.
If this new launcher version you have put up in github supporting the latest kivy version and sdl2 backend ?
Cheers.
JCG
Yes, the new launcher supports all the latest components. In fact you can also build the old launcher using sdl2 and the newest Kivy, I didn't realise the Play version still wasn't updated. Thank you for the notification.
You may consider stying put a bit. I looked into building the launcher myself but decided to wait. Video libraries do not compile right now. There are compilation errors coming from ffmpeg/ffpyplayer. This is precisely what I was looking to test in my application.
I wonder if there is a way to specify an older version of pyplayer/ffmpeg that compiles with buildozer.
Thanks for your support.
JC
@inclement so is the intention now to update the Play version of the Kivy Launcher?
Closing in favour of #1638.
Most helpful comment
I'm not sure what is the official status of the new launcher, but there should be no major barrier to having a python 3 version. Mostly, nobody has got around to creating and testing an official version yet. I'll try to make sure to include this as part of the next release.