MobileRead Forums - View Single Post

JimmXinu · 04-26-2014, 12:05 PM

For serious debugging of adapters, I use the CLI (command line interface) of FFDL and skip calibre all together. That way I'm not recreating the zip and restarting calibre every time I change something.

I'm on windows, so I have a run.bat file containing:

Code:

set PYTHONIOENCODING=UTF-8
c:\Python27\python.exe downloader.py -d %1 %2 %3 %4 %5 %6 %7 %8 %9

Then I just do 'run <url>'. downloader.py has other options as well, like -m for metadata only.

I also use lots of print statements (or logger.debug()) for debugging. The errors skb & Firedancer885 are reporting from their adapters are from not collecting or setting all the appropriate metadata.

If the track traces aren't enough to tell you which metadata you're not setting, I'd use print statements in the adapter to show what metadata you are setting.

04-26-2014, 12:05 PM	#2595
JimmXinu Plugin Developer Posts: 7,029 Karma: 4604637 Join Date: Dec 2011 Location: Midwest USA Device: Kobo Clara Colour running KOReader	For serious debugging of adapters, I use the CLI (command line interface) of FFDL and skip calibre all together. That way I'm not recreating the zip and restarting calibre every time I change something. I'm on windows, so I have a run.bat file containing: Code: set PYTHONIOENCODING=UTF-8 c:\Python27\python.exe downloader.py -d %1 %2 %3 %4 %5 %6 %7 %8 %9 Then I just do 'run <url>'. downloader.py has other options as well, like -m for metadata only. I also use lots of print statements (or logger.debug()) for debugging. The errors skb & Firedancer885 are reporting from their adapters are from not collecting or setting all the appropriate metadata. If the track traces aren't enough to tell you which metadata you're not setting, I'd use print statements in the adapter to show what metadata you are setting.