Debug calibre/plugins with visual studio

[Pr.BarnArt]

After trying for more than a day I have to ask what steps are needed totdebug calibre with visual studio 2017/2019.
I wanted it to use to migrate plugins for both python 2 and 3.
I tried all the things noted in: http://manual.calibre-ebook.com/develop.html and this https://www.mobileread.com/forums/sh...d.php?t=251201.
But they are based on VS2013.
I dit set CALIBRE_DEVELOP_FROM right and running calibre it uses the source code.
So I am stuck witch calibre 4.99 and the source of calibre-fork py3.
I only get: failed to attach debugger, Python interpreter not found.
Is there someone who can give me a lead.
(I also tried visual studio code,but without succes).

But after all just debuging calibre is not enough.
I need it for the plugins.
Which extra steps are needed to debug them, because plugins are zipped.

I am using win 7 - 64 bit, running calibre main on 32 bits and the 4.99.2 version at 64 bits. Debugging with python 3.6 or 3.7 64 bits.


Thanks in advance.

[kovidgoyal]

No idea, I've never actually used an IDE debugger myself, just print(). Why do you need a debugger?

[Pr.BarnArt]

Originally Posted by kovidgoyal

No idea, I've never actually used an IDE debugger myself, just print(). Why do you need a debugger?

I seems to me easier to analyse and correct code on the fly and run the new statement at once, steping back. I am used to c#.
Till now I indeed use print() and switch to editor, copy code and run calibre-debug again. I would like to avoid these steps ( talking about plugins).

[kovidgoyal]

Weel, as I said, I have never used one, but the error you point to indicates your IDE is unable to find a python interpreter. Debugging in calibre works by running a remote python debugger inside the calibre code and the connecting to it in your IDE.