On Mon, Dec 29, 2014 at 8:09 AM, Steven D'Aprano email@example.com wrote: >
On Sun, Dec 28, 2014 at 10:30:41PM +0100, Fetchinson . wrote:
On 12/27/14, Russell Keith-Magee firstname.lastname@example.org wrote:
This is an entirely reasonable approach if Kivy is what you want at the end of the day - but it's not what I want. I've been taking a much more atomic approach. The Kivy toolchain is also anchored in old versions of Python 2; something that definitely needs to be addressed.
I'm not entirely sure why Russell says this. Kivy claims to support Python 3:
Read the whole of that FAQ entry:
""" However, be aware that while Kivy will run in Python 3.3+, packaging support is not yet complete. If you plan to create mobile apps for Android or iOS, you should use Python 2.7 for now. """
That is - Kivy works on Python 3.3, but none of the tools that let you run Kivy on Android or iOS exist for 3.X. This is the hard part - the patches against Python and related libraries are non-trivial.
As far as I'm concerned python 2 is perfectly okay. If I don't need to
worry about python 3, what drawback does kivy have, if any, according to you?
Well, you've just lost me as a potential user. I have zero interest in legacy Python versions for Android.
For what it's worth, I agree. I'll probably end up supporting Python 2, but only because my currently working code (which is derived from Kivy's toolchain) work on 2.7; but my intention is to start focussing on Python 3 ASAP. IMHO there's no point starting a new project on a platform that has a known EOL on the horizon.
Yours Russ Magee %-)