Kivy 1.10.0 released
There appears to be a multi-step process to install Kivy on Windows. Isn&#x27;t the whole point of pip to not have to worry about that?<p>I was expecting &quot;pip install kivy&quot; &gt; &quot;python helloworld.py&quot; &gt; done<p>Instead I got &quot;install these things&quot;, &quot;if you&#x27;re using this version install this other thing&quot;, &quot;cool now install kivy&quot;.<p>I went ahead and tried to package a Windows app using their recommended method (PyInstaller), and PyInstaller doesn&#x27;t support current version of Python.<p>Thought I&#x27;d take a look at other offerings, for iOS there&#x27;s a weird project-mirror XCode generator script. Android isn&#x27;t any better.<p>I mean, this is more of a reflection on the disparity across different platforms and packaging tools rather than Kivy itself. There&#x27;s a reason some large Enterprises won&#x27;t touch all of these tiny, moving, fragile tech.<p>In saying all of that, I think Kivy has some very nice points. The examples are straightforward, and to-the-point, covering a lot of use cases. However I think having this as a &gt;1.0 versioned release is kind of crazy. When comparing this to other frameworks, why would you ever choose this? Aside from &quot;I like Python&quot;? Definitely shows a lot of promise, but I think sitting in sub 1 state for a while like Rust until you&#x27;ve got something going for you would help with adoption and on-boarding.<p>EDIT: Tried to use PyInstaller from source, no luck - SDL required. Found a closed bug report which explains how to fix it - the &quot;optional&quot; library has to be installed for PyInstaller to work. Go figure. <a href="https:&#x2F;&#x2F;github.com&#x2F;kivy&#x2F;kivy&#x2F;issues&#x2F;4482" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kivy&#x2F;kivy&#x2F;issues&#x2F;4482</a>