PlexConnect is working well so far except it shows ((ERROR:VAL)) for some metadata. Found a topic about running PlexConnect in OS X and it talked about launching it with Python 2.7. When I setup PMS and PC on CentOS 6.4, I found a guide for installing Python 2.7 but it basically said that it should be installed separately instead of overwriting the default Python install. So PC is launching with the default install of 2.6 but I can also run it with 2.7.
Anyone know what has to be changed in the PlexConnect and/or Screen daemon launch settings so that it launches using Python 2.7 instead of the default install? I have no idea what to change and don't want to break my server which is finally running great.
Almost all of the python files should live in their respective folders (C:\Python26 and C:\Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.
uninstall 2.6
Open the installation file of your previous version, it must be a .msi file.
When the window opens, two options will be displayed: "Repair" and "Remove"
Select "Remove" and click "Finish"
OR
Go to the control panel.
Click "Add or remove programs
Select the Python version from the installed program list and click "Uninstall."
Almost all of the python files should live in their respective folders (C:\Python26 and C:\Python27). Some installers (ActiveState) will also associate .py* files and add the python path to %PATH% with an install if you tick the "use this as the default installation" box.
uninstall 2.6
Open the installation file of your previous version, it must be a .msi file.
When the window opens, two options will be displayed: "Repair" and "Remove"
Select "Remove" and click "Finish"
OR
Go to the control panel.
Click "Add or remove programs
Select the Python version from the installed program list and click "Uninstall."
Then 2.7 should be the default.
If this was on Windows or OS X I'd know how to fix it but I'm running PMS and PC on CentOS. I don't see anything resembling a path specifying where Python is in any of the PC scripts, so it's using the default install. I just need to tell the Screen daemon and/or the scripts where the Python I want it to use is.
Opps sorry about that. I read your post wrong. Thought it was a pc. Try this.
First off you need to recognize yum’s dependency on Python 2.6. Simply replacing this will break your passing semblance of a package manager. We will be using this later so not breaking is the preferred path. Python versions can live in relative harmony together. Download the Python source and untar it to some directory. I use /opt or ~/source for all of my non-native additions. You can choose whatever you want.
[root@server] tar -xf Python-2.7.1.tgz<br>
[root@server] yum install gcc
[root@server] ./configure<br>
[root@server] make
[root@server]$ make altinstall
The altinstall part is key, as it will resist installing the binary to the default /usr/bin/python path, overriding the needed 2.6 version of Python. On CentOS installation it put it in /usr/local/bin/python2.7. It should be accessible by using python2.7 wherever you use python.
I already did that. I have Python 2.7 as a separate install and it works.
Now I need to know what I have to modify in the PlexConnect scripts so that it is launched using 2.7 and NOT the default install. Also need to know if anything with PC running as a daemon at boot with Screen has to be changed.
I already did that. I have Python 2.7 as a separate install and it works.
Now I need to know what I have to modify in the PlexConnect scripts so that it is launched using 2.7 and NOT the default install. Also need to know if anything with PC running as a daemon at boot with Screen has to be changed.
I have a machine running Linux too. This is what I did to get mine to use 2.7 as default. Sorry this is what worked for me. My main server is OSX. But I also have one on windows too
I know that's how I'd start it manually from the command line but I'm running it as a daemon from the linked instructions in the first post. No clue what I have to change so it'll use python 2.7.
I have a machine running Linux too. This is what I did to get mine to use 2.7 as default. Sorry this is what worked for me. My main server is OSX. But I also have one on windows too
I did the same thing but all that does is install Python2.7. It doesn't change anything so it's used as the default install. And based on what I've read and what you said about the 2.6 dependency, setting up 2.7 as default would break that.
I am in the same boat. if I manually start it using >python2.7 ./PlexConnect.py it works perfectly, need some way of setting up a service type wrapper to make it run under 2.7 permenantly on boot now. Brilliant job by the way, I actually sold my ATV3 due to lack of support for anything useful (besides netflix) and managed to get it back now this works so well.
