Make it clear that python3 can still be debugged by winpdb

[noamraph]

Hi, The README file starts with "WINPDB ON PYTHON 3 IS BUGGY AND NOT WORKING". It makes it seem like winpdb is useless for python3 users. However, I understand that this means that the GUI doesn't work on python3, but rpdb2.py does. So python3 code can be debugged by importing rpdb2.py from python3 and connecting to it from winpdb on python2.

I suggest to make this clear - I'm a heavy user of winpdb, and I am working on migrating my code from python2 to python3. This note made me think that it will mean that I have to either stop using winpdb or start working on a fix, and it's not the case.

Thanks for the good work! It helps me a lot! Noam

[bluebird75]

Thanks for the feedback. Could you propose a better wording ? I tried to describe the current situation but it's not that easy... Using winpdb with Python 3 is not trivial either, and I believe there are some subtle bugs lying there, like not all variables showing up.

[noamraph]

First, I would try to make it as easy as possible to debug python 3 programs. I think this just means that if you run "winpdb something" and something is a python3 program, winpdb should know to run it from python3 even though it is in python2.

Then, I may write something like this: Python 3 support - help needed: currently it's possible to debug python3 programs using winpdb, since the underlying rpdb2 module supports python3. However, the winpdb GUI currently only works on python2. I would appreciate your support in making it work with python3. Also, I suspect there are some subtle bugs with using rpdb2 from python3 (like not all variables showing up), so please take notice and report anything you find.

Thanks!

On Thu, Aug 16, 2018 at 11:05 PM Bluebird75 [email protected] wrote:

Thanks for the feedback. Could you propose a better wording ? I tried to describe the current situation but it's not that easy... Using winpdb with Python 3 is not trivial either, and I believe there are some subtle bugs lying there, like not all variables showing up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bluebird75/winpdb/issues/15#issuecomment-413668094, or mute the thread https://github.com/notifications/unsubscribe-auth/ABe0OO-PWRsnlnd-LGf6ZjGfAzvsATmcks5uRdB-gaJpZM4V9vN- .

[bluebird75]

For automatic Python 3 support, it is very delicate. It is sometimes possible that a program is Python 3 dedicated, but not always. And some program are designed to run on both Python 2 and Python 3. Still, I agree that there could be some heuristics to detect this and popup a dialog.

From the GUI, if you use the "File / Open script" menu entry, you can choose with which interpreter to run your program.