Note that python3.4 is pretty old - in particular 3.5 fixed a few things - and 3.6 has been out a little while. So for anyone else that's coming into this for t

Note that python3.4 is pretty old - in particular 3.5 fixed a few things - and 3.6 has been out a little while. So for anyone else that's coming into this for the first time, I'd recommend the latest stable, official python (3.6.1 at the time of this writing). The official python is built with/works with Visual Studio (the community version works fine) - and with hooking off "add python to path" in the python installer along with first installing Microsoft Visual studio command line build tools/compiler -- most regular python packages should install nicely with with pip. For your own sanity, please do use "virtual environments" (venvs) -- now officially part of python: python -m venv kivy-venv Will create a python3 venv in a folder called "kivy-venv" -- that can be activated in powershell via the script: "kivy-venv\Scripts\Activate.ps1". Then commands like "pip" will be run in the context of that venv, and not mess with system python. For reasons I don't fully understand, the official python binary on all other platforms, post python 3, is "python3", while on windows it remains "python". This leads to some additional conflicts on windows if both python 2 an 3 are installed. You can also install python in your user profile - and if you do so, running the default installed pip outside of an activated python virtual environment will mess up your install (and/or fail). Always use a venv when doing anything in python. The only exception is if you're creating your own linux/os distribution, and want python to power part of your distribution tooling (eg: the package manager, like "apt").