For those of you who like living on the bleeding (and buggy) edge of the software world I have uploaded a version of Winpdb compatible with Python 3.0beta1 and Python 2.6beta1 to the mercurial repository: http://winpdb.org/cgi-bin/hgweb.cgi. Instructions are available at http://winpdb.org/cgi-bin/moin.cgi/WinpdbSource
If you find anything that got broken with this update please let me know.
Keep in mind that you can’t actually run the Winpdb GUI in Python 3.0 since wxPython is not available for that version yet. What you should be able to do is to start the debugged script in Python 3.0 and attach to it from a Winpdb instance running under Python 2.5. On a Windows system you would do it with something of this sort:
c:\python30\python.exe rpdb2.py -d myscript.py c:\python25\python.exe winpdb.py
For this to work you need to either install the debugger into both Python installations or not install it at all. Remember that you can use Winpdb without installing it. In any case you must not try to run a copy of Winpdb installed into one Python version with the interpreter of another Python version.
Heads up for the Python development team: If you run idle.py in either Python 3 or 2.6 under the control of a debugger (any debugger including pdb.py) an erroneous exception is raised in line 295 of multicall.py due to a bug in the interpreter. I will try to be a good citizen and file a report this week. If I didn’t do it it is probably because the dog ate my notebook.