Am 2015-08-18 11:54, schrieb Shai Efrati:
> Thank you Andreas for your answer. I now understand much better why
> and what can be achieved using PuDB.
> I wonder if someone here faced a similar situation (debugging pyc/pyo
> files) and have the right tool for the mission. A colleague of mine
> uses WingIDE for that, so he run the debugger on py files in his IDE
> against remote pyc files. Is there a non-IDE solution?
Oh, now I understand much better what you're asking for. Correct me if I
am wrong, but what you're asking for is to have the debugger retrieve
the source from somewhere that is not the installation location of the
code, correct? If so, that should be possible, although it is not
currently implemented, and in fact that should be quite easy. I would be
happy to take a patch.
Am 2015-08-18 07:35, schrieb Shai Efrati:
> Dear Pudb users,
> I try to debug pyc/pyo files, but fail because of Non-ASCII
> characters ('\x1d').
> Pudb does run against the py files, but due to limitations in the
> specific environment, i need to run it on pyo/pyc files.
> Did anyone faced this issue? do you have any idea / solution?
PuDB being a source-level debugger, I am not sure how much success you
will have without having the source code of the program that you are
debugging. In particular, I am not even sure what PuDB should show on
the screen while you are debugging a non-source program. And since PuDB
is mainly a visual debugger, its main benefit lies in what it shows on
the screen. Or maybe I'm just lacking imagination for what you want. In
that case, maybe you could describe what you would like the tool to do.
Sorry to disappoint, and I hope you find something that suits your
Dear Pudb users,
I try to debug pyc/pyo files, but fail because of Non-ASCII characters
Pudb does run against the py files, but due to limitations in the specific
environment, i need to run it on pyo/pyc files.
Did anyone faced this issue? do you have any idea / solution?
Thanks in advance!