Yeah that was my point.
Maybe Baa or Roidy can chime in on this but I think that trying to make the actual changes on the actual 10.6 installation would be best, especially if it is not trivial and 10.9 is out soon.
Out of interest is there a reason you are still running 10.6, is it because your hardware is not compatible with later versions?
I'm running 10.6.8 Server on my Mac Mini. It's only a 1.83 GHz Mini with 3 GB of RAM, so I'd rather not cripple it's performance with Mountain Lion Server; Snow Leopard runs notably faster on older, RAM-limited machines. Also, I don't relish the idea of reconfiguring all my server settings from scratch because you can't really migrate 10.6.x server to 10.8.x server. And finally, OS X 10.6 allows me, via Rosetta, to run older "universal binary" software that I still occasionally need.
Out of interest is there a reason you are still running 10.6, is it because your hardware is not compatible with later versions?
My hardware is oldish but reportedly can handle Mountain Lion. I just like Snow Leopard and have had no reason to upgrade. Was thinking I might when Mavericks comes out. I generally tend to be conservative with upgrades both of hardware and software. If it works why change it, is generally my philosophy.
I was wondering if my Plexconnect is using a different version of python than terminal indicates (I know that 2.6 is the Snow Leopard 10.6.8 default python environment). Is there a way to check what version of python a specific app is using? Can't seem to find this online.
PlexConnect uses the one in "/usr/bin/python" - when doubleclicked (Win) or started with "./Ple...". We might change this into "/usr/bin/env python", which then would pick the first python on your path...
I just tried this approach by replacing "/usr/bin/python" in the Plexconnect.py with "/usr/bin/env python" and it didn't work for me. Plexconnect selected python 2.6 (the display error reappeared) rather than 2.7.
I will stick to changing it to /usr/local/bin/python for now.
PlexConnect uses the one in "/usr/bin/python" - when doubleclicked (Win) or started with "./Ple...". We might change this into "/usr/bin/env python", which then would pick the first python on your path...
I checked my bash_profile file and it has 2.7. So I re-edited Plexconnect.py with the usr/bin/env python line and it worked this time. Must have been a cut and paste error earlier.
Also, I don’t need 2.6 but I believe Snow Leopard does.
I checked my bash_profile file and it has 2.7. So I re-edited Plexconnect.py with the usr/bin/env python line and it worked this time. Must have been a cut and paste error earlier.
Also, I don't need 2.6 but I believe Snow Leopard does.
How are you starting PlexConnect? Via the Terminal, AppleScript, or launchctl?
