Page 1 of 1
Different Python version causes conflicts with postprocessing?
Posted: August 29th, 2009, 3:12 am
by qwerty967
I just upgraded to Snow Leopard and tried to switch my postprocessing script from
to
and this error came up:
Code: Select all
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/Volumes/thor/scripts/postproc.sh", line 10, in <module>
import glob
ImportError: No module named glob
Is this a bug?
Re: Different Python version causes conflicts with postprocessing?
Posted: August 29th, 2009, 3:53 am
by switch
Sounds like your install of python does not have glob installed. What is the contents and purpose of /Volumes/thor/scripts/postproc.sh ?
Moving to the general forum as this is not a sabnzbd bug.
Re: Different Python version causes conflicts with postprocessing?
Posted: August 29th, 2009, 10:01 pm
by qwerty967
I am using the default Python installations (2.5 and 2.6) that ship with the recently released Snow Leopard. I've switched all my miscellaneous Python scripts from using 2.5 to 2.6. The only thing that gives me an error is my custom post-processing script for SABnzbd. Running the script from the terminal does not yield this error, however, SABnzbd running it as post-processing does.
It's no big deal. Running it under 2.5 works, but 2.6 throws an error on the first import statement. glob, os, re, they all fail except for sys.
Re: Different Python version causes conflicts with postprocessing?
Posted: September 11th, 2009, 2:55 am
by madd
I'm getting the same error using Snow Leopard.
The post-processing scripts run perfectly fine if executed from command-line using ie Terminal.
qwerty967 wrote:
I just upgraded to Snow Leopard and tried to switch my postprocessing script from
to
and this error came up:
Code: Select all
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "/Volumes/thor/scripts/postproc.sh", line 10, in <module>
import glob
ImportError: No module named glob
Is this a bug?
Re: Different Python version causes conflicts with postprocessing?
Posted: September 11th, 2009, 3:07 am
by qwerty967
A couple people are reporting errors with the default Python in Snow Leopard and this post-processing script:
[Linux, MacOSX, Windows] Media Processing + XBMC Updater.
Re: Different Python version causes conflicts with postprocessing?
Posted: September 11th, 2009, 8:37 am
by zakharm
I'm also having problems when using Snow Leopard with my
album art script
Code: Select all
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "write_album_art.py", line 26, in <module>
import sys, os, fnmatch, re, urllib, eyeD3, shutil, string, ConfigParser
ImportError: No module named os
Re: Different Python version causes conflicts with postprocessing?
Posted: October 10th, 2009, 5:41 am
by Camelot
I am now having the same issue. Anyone find a fix?
Re: Different Python version causes conflicts with postprocessing?
Posted: October 10th, 2009, 10:02 am
by shypike
It looks like Apple made a serious error with their Python version.
Raf (our OSX maintainer) is looking into the matter.
It also affects compiling SABnzbd for OSX.