View Single Post
Old 04-07-2025, 04:58 PM   #91
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,858
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi BeckyEbook,

I will look into that. I did add a new Sigil Error box that allows full expansion to see any python exceptions and debug output if a runtime error happens. But if no runtime error happens, then no output will be shown.

You should always be able to redirect all python print output to a file at a fixed path no matter what. Have you tried redirecting python std out to a file? Is the file empty? Did you use a hard coded path?

I may be able to create a log ability of some sort stored in the python function context that the C++ side creates.

I will try playing around with it a bit to see.

Kevin



Quote:
Originally Posted by BeckyEbook View Post
The functions have potential, but I have trouble debugging them.
"print" or trying to save information to an external debug file does not work.

If I need any "output" I am helpless.
What can I do?

I checked in Calibre and there is a special window with results, so that such a function works.

There are certainly people who are able to write a working function right away. I like to test my solutions, so "print" is my friend.
KevinH is online now   Reply With Quote