How to setup Python debug environment for Calibre Recipes

[huang5307]

I am trying to develop a recipe. I want to setup a Python debug environment for Calibre Recipes (in Windows 8.1).

Firstly, I include Calibre lib to Python IDLE but still failed. Does anyone know to do that?

>>> sys.path.insert(0, r"C:\Program Files\Calibre2\pylib.zip")
>>> from calibre.web.feeds.recipes import BasicNewsRecipe

Traceback (most recent call last):
File "<pyshell#4>", line 1, in <module>
from calibre.web.feeds.recipes import BasicNewsRecipe
File "site-packages\calibre\__init__.py", line 17, in <module>
File "site-packages\calibre\constants.py", line 203, in <module>
File "site-packages\calibre\constants.py", line 187, in __getitem__
File "site-packages\calibre\constants.py", line 162, in load_plugin
AttributeError: 'module' object has no attribute 'extensions_location'
>>>

[eschwartz]

Just run calibre via "calibre-debug -g" to get debug output.

Alternatively, run "calibre-debug" to get an interactive python console that can access calibre's code. You cannot simply add the calibre source code, you need it to be properly installed which is difficult as it is a binary install. That is why calibre includes its own python console.

On linux, you can do a source install (for instance the repo packages) -- that would allow you to run bog-standard python debugging tools which can call on all of calibre's code.

[huang5307]

Originally Posted by eschwartz

Just run calibre via "calibre-debug -g" to get debug output.

Alternatively, run "calibre-debug" to get an interactive python console that can access calibre's code. You cannot simply add the calibre source code, you need it to be properly installed which is difficult as it is a binary install. That is why calibre includes its own python console.

On linux, you can do a source install (for instance the repo packages) -- that would allow you to run bog-standard python debugging tools which can call on all of calibre's code.

actually, I try to do this is because I want to develop a recipe to handle soem web need username / password to access. Do you have any suggested documents for study.

[Divingduck]

Take a look on the sticky posts at the top of this forum and calibre help for adding news: http://manual.calibre-ebook.com/news.html. There is an additional section at the end of this help called API documentation for recipes. Very useful. At least it is maybe a good idea to take a look to the command line interface help: http://manual.calibre-ebook.com/gene...cli-index.html

I use for recipe development two simple batch files in a working directory like "Your_Recipe" what runs the recipe via command line:

Your_Recipe.bat:

call Delete_Your_Recipe.bat
ebook-convert Your_Recipe.recipe .epub -vvv --debug-pipeline debug > Your_Recipe.log

And Delete_Your_Recipe.bat:

rmdir debug. /s /q
del Your_Recipe.epub
del Your_Recipe.log

The first batch file call a delete-batch for all previous created debug and log files if available and start then the recipe in debug modus and collect all screen printed information’s in a log file.
-vvv defines the level of verbosity
The second batch simply delete all created directories and files (debug- and log files)

[eschwartz]

Kovid mentions on the development page in the user manual, his preferred debugging tool is liberal use of print statements in the source code. Why not try that?

[Terisa de morgan]

Originally Posted by eschwartz

Kovid mentions on the development page in the user manual, his preferred debugging tool is liberal use of print statements in the source code. Why not try that?

That's the oldest (and usually most useful) way to debug a code.

[huang5307]

Originally Posted by Terisa de morgan

That's the oldest (and usually most useful) way to debug a code.

If there any way we can using IDE tools to develop recipe that would be very easy to understand the secret of Calibre recipes.

[eschwartz]

They aren't a big secret... anyway, what exactly do you want to see in the IDE that you cannot do with print statements? Considering recipes need to be run through ebook-convert anyway...

[DanielBonnery]

Hi,
I tried to follow
https://manual.calibre-ebook.com/develop.html.
But at some point I failed to test the recipe from the ide. Using the ebook-convert command is a pain. Thank you for the comments "Why don't you use print statements". It would be nice to have an answer to the original question for those who do not want to use print statements.

Bests,
Daniel

[DanielBonnery]

I found this:
http://jb-blog.readthedocs.org/en/la...-your-IDE.html
I followed the links but I could not have icu properly working...
I gave up at the end.
The print statements solution is really annoying, a button to test the recipe directly in the editor would be great. Now each time I test, I save and close the editor, run the fetch all news button, open the tasks windows, select the task, click to show log, close, reopen the editor ...