I had a lot of trouble getting Pcbnew and the footprint editor to work, even in earlier versions from last year. It kept crashing and closing KiCad without error output.
I finally found the solution by changing my default Python version in Windows 10 environment variables (PATH, PYTHONHOME) to Python 2.7 (previously 3.4). My issue is that I’m working with 3.4 on other projects and hate to have to constantly shuffle around my configuration every time I want to use one or the other software. Is there any way to configure my KiCad installation to use my Python 2.7 installation without going through the system’s environment variables?
Isn’t KiCAD using the python that is in it’s own installation folder?
C:\Program Files\KiCad\lib\python2.7
I got python 2.7.11 installed on my win7 system and the command line in PCBnew is reporting 2.7.10, so for me it’s definitely not using the system python, but it’s own…?!
Running a command line in
KiCad tried to run its scripts with my default Python 3.4 installation. The environment variables PATH, PYTHONHOME and PYTHONPATH seem to block the program from selecting its local version. I fixed it by removing those variables entirely, which is actually recommended according to the internet. It doesn’t interfere with my other Python 3 programs so far, so that’s good.
(On a side note: I also once set the env. vars to my machine’s Python 2.7 installation, which made me able to run Pcbnew, but with some error messages on startup which did not seem to affect functionality on brief inspection.)
All that is needed is some dependency (i think wx stuff) to be available under windows for python 3 (I think nearly all linux distros are already on python 3) I am not sure the KiCad project itself can do much about it unless it takes over the “support” for yet another library.