On 12/29/14, Steven D'Aprano
On Sun, Dec 28, 2014 at 10:30:41PM +0100, Fetchinson . wrote:
On 12/27/14, Russell Keith-Magee
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:
http://kivy.org/docs/faq.html#does-kivy-support-python-3-x
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.
I sympathize with your approach and I'd probably take the same attitude but so far I'm only using python 2 projects and developing for python 2 only (unfortunately). Cheers, Daniel
-- Steven _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
-- Psss, psss, put it down! - http://www.cafepress.com/putitdown