On 12/27/14, Russell Keith-Magee <email@example.com> wrote:
> So, that's what I've been working on. Since I posted to Python-ideas in
> October, I've been focussing on getting the patches necessary for Python's
> own build system. However, I've been distracted by work life etc, so I
> haven't made as much progress as I would have liked. I'm hoping the
> Christmas/New year break will give me a chance to make some headway.
> As far as Kivy goes - I have tinkered with Kivy; I've even used Kivy's
> tools as a starting point for some of my own efforts. However, to me, Kivy
> is focussing too far up the stack - their toolchain appears to be based on
> getting *Kivy* working on mobile, not *Python*.
What do you mean by this exactly? I thought kivy = python + some
libraries. So if kivy works on android that necessarily means that
python itself works as well, doesn't it?
I thought I'd use kivy even
if I don't need any of their fancy libraries only a basic python
installation, but you'd say this is not a good approach?