Quote:
Originally Posted by JimmXinu
Given where this error is occurring, I don't think it's to do with network.
On some platforms, calibre is remarkably fussy about print statements in the code that runs in the background job and that line number is for a debug print when a certain exception is caught.
The attached version changes the print to a proper logging output instead. I don't see these problems myself so I can't promise this will fix it, but I think it will.
|
I'm grabbing it now, and will report the news.
Edit: since you mentioned that it might be platform specific, I'm on OSX Mavericks, in case that helps with anything.