Hi, Adam. Funny you should ask that now. I just noticed that some changes went in recently that completely breaks python scripting on OS X. I haven’t had a chance to look too deeply at it, but it looks like a check was added on the return of wxversion.select(), which was likely always failing in the past, but it didn’t matter because Bernhard had done all the work in packaging to make sure the library paths all worked. Now it fails this check, popping up an error dialog which kinda hoses your kicad instance at that point.
In general my feeling is that we should just move forward with the scripting build, assuming the immediate issues are worked out. It is a released feature and the more eyes and fingers on it the better, I say.
Garth
On Jul 2, 2015, at 6:30 PM, Adam Wolf<adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi folks,
I currently build both non-scripting and scripting Mac nightlies. I am thinking it is time to stop building non-scripting and move the scripting builds out of DEBUG. They don't work perfectly, but I thinking having more folks use them will help expose the bugs that do exist.
Thoughts?
Adam Wolf
Cofounder and Engineer
W&L
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
