I couldn't leave well-enough alone.
On a system running Yosemite OSX, I installed Homebrew.
Then I proceeded to install Python3.5 plus pip, plus Qt, PySide, Zeroconf, and PythonOSC. Something, I forget which, wanted Python2.7, but didn't seem to want to work with the native Apple Python. So, I brewed a Python2.7.
Then PythonOSC didn't want to work with Python2.7. So, I found a git fork that did work. I got it all going, and was quite pleased with the way py2app made a nice clickable app with my custom icons.
THEN. I tried to install Kivy-iOS. Mistake. It wanted native Apple Python (and a whole lot of other fussing). Eventually, I thought I'd undone all the Homebrew Python2.7 stuff and it's bastard children modules, packages, whatever, and gotten them all working with native Apple Python.
Almost. My app works fine from the command line but will not package with py2app, claiming that it's missing my custom installed PythonOSC module.
Anyone know how to extricate myself from this without starting from scratch? How can I find the difference between what the command line sees as the path and what py2app sees?
"Unusual claims like evidence for alternate universes require a very high burden of proof," Chary noted in the study.
The understatement of multiple universes.
"Bring out your dead."
White House to announce its first-ever Maker Faire
The maker movement is coming to Washington. Inspired by a kid and a marshmallow cannon, the White House is fully embracing DIY with the inau
The first 3D-printed plastic car is as strong as steel and half the weig...
These new 3D-printed cars can use less parts and lighter materials to offer the same functionality and safety with less complexity and energ