Winpdb - A Platform Independent Python Debugger Download
The latest version is Winpdb 1.4.6 Tychod.
Winpdb for GNU/Linux
To use Winpdb in GNU/Linux you need to install wxPython 2.6 or later. Most distributions include wxPython as a package called python-wxgtk. Use your distribution’s package manager (e.g. synaptic, aptitude or yum) to find and install it.
Download the Winpdb source package and extract it’s content into a new folder. Enter the new folder from a terminal window and type: sudo python setup.py install -f
Alternatively use a terminal with admin privileges and type: python setup.py install -f
Winpdb for Windows
To use Winpdb in Windows you need to install the wxPython runtime (The unicode version is preferred). Once wxPython is installed, users of Python 2.5 should download the Winpdb installer and launch it. Users of Python 2.6 or Python 3.0 should download and install the Winpdb source package.
Notes
- You can use Winpdb without installing it by running winpdb.py.
- You can use rpdb2.py, the command line debugger included with Winpdb, without installing wxPython.
Recent Changes
April 7, 2009 - Winpdb 1.4.6 Tychod
Bugs Fixed:
- Major Bug fix: Handle debugging of run-away recursions.
- Compatibility with Python 3.01.
I’ve appreciated previous versions of winpdb. For 1.1.4, released a few hours ago, I downloaded the win32.exe installer, but Windows Vista 64-bit did not recognize it as a valid executable. My Windows did recognize 1.1.2. Thanks for a sweet debugger.
– Ethan
Problem fixed. It was the result of uploading the exe file as ASCII.
Thanks for this report.
–Nir
I’ve been trying to use WinPdb with SPE 0.8.3 (the bundled version of WinPdb is 1.0.6)
when I launch WinPdB on Windows XP, (Python 2.5) a console window (empty) and a debuggee console (empty) appear, then the WinPdb GUI. The following appears in the GUI console:
…
*** Password has been set to a random password.
*** Spawning debuggee…
*** While attempting to find debuggee, at least one debuggee denied
*** connection because of mismatched passwords. Please verify your password.
(x 3)
…
*** Debugee failed to start in a timely manner.
I’ve tried the same thing on Ubuntu Edgy (Python 2.5) - The “password” stuff doesn’t appear, but I still get the final message, ie “Debugee failed to start in a timely manner.”
Do I need to set an SPE or debuggee password to match the WinPdb one, and if so how?
Thanks for your help!
Hi Charles,
If possible use SPE from subversion, to which I am going to add now the latest winpdb:
svn checkout svn://svn.berlios.de/python/spe/trunk/_spe
More info here:
http://pythonide.blogspot.com/2007/02/how-to-download-latest-spe-from_26.html
Otherwise, you can upgrade easily winpdb, by removing the old _spe/plugins/winpdb folder and replacing it with the newer one. Also you need to put an empty __init__.py in the winpdb folder. Probably your problems are related to the old version of winpdb.
I am not looking here around often. So you better contact me on the spe-user list.
Stani
Hi, It would be nice if you could put here the exact command how to get it using svn.
It’s this command:
svn co https://winpdb.svn.sourceforge.net/svnroot/winpdb winpdb
If you are only interested in the lastest version, like me, it’s actually this command:
svn co https://winpdb.svn.sourceforge.net/svnroot/winpdb/trunk/winpdb winpdb
If anyone’s interested, I rolled an app bundle for OS X using Platypus. The entire 1.3.2 distro is in the resource fork. If you install the correct wx version, you should just be able to download and run the app.
Any chance of putting this package on the download page?
If there’s any interest, shoot me an email at elessar at nienna dot org.
Caveat 1: Platypus requires Mac OS 10.3.9 or later.
Caveat 2: I only tested with MacPython 2.5. I just made sure that all the modules are loaded. I haven’t thoroughly tested Winpdb for Mac-related issues, I just re-packaged the code.
Caveat 3: If you want to use the app from an account other than the one you use to install it, you might need to run it once from the installing account to compile the python source in the resource fork for whatever version of python you’re using.
Confirmed working for Leopard 10.5
can anyone tell me that this debugger will highlights the errors in colors or in any other format? offcourse the Errors should be run time .I need this information since i am working on developing debugger of stated kind. If anyone know abouts debuggresof any lang . of such kind - should highlights the errors lines by colors or other thing so one can easlly indentify errors in large codes-please tell me.
I download winpdb-1.4.0.win32.exe. My python is checked into a dev tree under source control, so it does not necessarily have any registry settings. When I try to install I get “No python installation found in the registry” and then a dialog for “Python Directory” and “install directory” But I cannot type any text into either box (to point it at my python install dir). So I can’t install.
Hi Ron,
I suggest you use Winpdb without trying to install it. Simply extract it into a folder of your preference and run it from there.
But where do I get it? I can’t “extract” from the winpdb-1.4.0.win32.exe. Is there a .zip sitting around some place?
Maybe I”m not being clear. I can’t install install at all. I get to the dialog I mentioned, and I cannot type anything in for the paths requested. My only options are ‘back’ and ‘cancel’
You need to download the source package (read the page above). It is a TAR archive and if you do not have an archive manager that can read it, download and install one such as the Free Software 7-zip.
WinPDB doesn’t recognized as valid EXE
[...] Download [...]
is there any to invoke winpdb on the remote system from emacs tramp? esp without any need to add a password by hand
Is there any way to autostart the client end to hook up to first (or only) remote instance?
thanks
Hi,
I am running Mac OS X with Python 2.5.1, I need to keep this version because another library is needs this particular version.
Is there a chance you can make the version that works on this platform available?
I saw that Matthew Fitzgibbons created a version and put it in ‘Resource Fork’ I assume that was before the move to googlecode for hosting…
Could you please add that old version from SF to GoogleCode? When I go onto the SF site it redirects to this one!
Thanks
[...] best tool I found on Windows environment for Django/ Python Debugging is : WinPDB, Just download and [...]
[...] Download [...]
Hello, downloaded the winpdb.exe file, and when trying to install it says:
“No Python Installation found in the registry”
which I don’t understand, because I do have python 2.6.2 installed on my PC(running windows XP 64 bit.) Any idea please?
Thank you in advance.
hmm… it was built with python 2.5 so this is probably the source of the problem.
I think I will stop distributing the exe installer.
Try the source archive. Installation from source is simple enough.
@Paul
There’s an outstanding problem with Python 2.6.x on 64-bit editions of Windows, in that it is unable to determine that current Python installation using the registry. Please see the following for more info: http://bugs.python.org/setuptools/issue2. This means easy_install, and in fact distutils, is broken on 64 bit Windows w/ Python 2.6.
I’m using Windows 7 x64 and this was sufficient reason for me to abandon the 64 bit version of Python 2.6 for now.
@nir
In fact I’ve just confirmed the .EXE installer for WinPDB works on the 32-bit version of Python 2.6.4 on Windows 7 x64. It’s very likely that Paul encountered the distutils bug in Python 2.6.x, not any problem in your .EXE distribution.
YMMV.
I am a total newbie to Python, just trying to get up to speed for a project we are doing at work….
Two days after downloading it, winpdb is already indispensible.
(Because it took 1 1/2 days for me to RTFM and figure out how to attach to my pitiful, lame attempt at a program.)
Damn! Great tool!