[0.7.17b1] post-processing scripts always fail

[jcfp]

To reproduce: queue a job with any post-proc script. Upon job completion, the history says "PostProcessing was aborted (see logfile)", and the following is logged :

2013-12-14 22:57:19,652::INFO::[newsunpack:212] Unrar finished on /home/jp/downloads/incomplete/random2
2013-12-14 22:57:19,653::DEBUG::[newsunpack:1399] build_filelists(): joinables: []
2013-12-14 22:57:19,653::DEBUG::[newsunpack:1400] build_filelists(): zips: []
2013-12-14 22:57:19,653::DEBUG::[newsunpack:1401] build_filelists(): rars: []
2013-12-14 22:57:19,653::DEBUG::[newsunpack:1402] build_filelists(): ts: []
2013-12-14 22:57:19,653::INFO::[postproc:346] unpack_magic finished on random2
2013-12-14 22:57:19,655::ERROR::[postproc:502] Post Processing Failed for random2 ()
2013-12-14 22:57:19,655::INFO::[postproc:504] Traceback:
Traceback (most recent call last):
File "/tmp/t/SABnzbd-0.7.17Beta1/sabnzbd/postproc.py", line 437, in process_job
nzo.nzo_info.get('failure', ''))
File "/tmp/t/SABnzbd-0.7.17Beta1/sabnzbd/newsunpack.py", line 136, in external_processing
str(nicename), str(msgid), str(cat), str(group), str(status). str(failure_url)]
AttributeError: 'str' object has no attribute 'str'
2013-12-14 22:57:19,991::INFO::[postproc:535] Cleaning up random2 (keep_basic=True)

The script used seems irrelevant; the above was generated with the example script that just print its own arguments. Full job debug log available if needed.

Side effect of this? https://github.com/sabnzbd/sabnzbd/comm ... c4f2cd1f93

[shypike]

Oh damn, I think I know what it is.
Thanks for the report.