Support Forum

My interpretation of running post-processing Python scripts associated with SABnzbd is that they'd be called using the same Python interpreter, rather than using what could be a different installation (and in my case, is). How this operates wasn't obvious until reading the code, but now that I know ...

Okay, well in my specific case, the system executable of "python" is Python 2.4, whilst I've compiled my own Python 2.7 to run SABNzbd. The post-processing scripts from SickBeard are no longer Python 2.4 compatible and hence the issue. The same issue for would apply for anyone with a syste...

In the sabnzbd/newsunpack.py file (line 141-142), the execution of external Python files can be inadvertently run using a different interpreter than the one that started SABnzbd. Firstly, the insertion of the 'python' command is hard-coded for WIN32 systems, which may result in the executable not be...