Debug python for Windows?

[Sean Slattery]

> Hmm.  You didn't mention installation last time, and I'm 
> unclear on your
> meaning.  If you're just trying to test code, installation in any
> conventional sense isn't needed:  the Python you just built 
> runs fine from
> the PCBuild directory.  No file copying, moving, or 
> registration is needed.
> If you're building extension modules of your own, it's 
> conventional to plant
> a copy of their DLLS in the PCbuild directory too (so the 
> freshly built
> Python there can find them).

I guess I should have mentioned installation more than once in the original
email - my bad.

If anyone believes they need a "debug installation" of Python (and I figured
it was the best way for me to get started debugging a wxPython issue I was
having), then following installation steps worked for me. (By worked, I mean
mimiced an ActiveState installation and was immediately usable by the
wxPython build+install process)

1. Build the bits you need (we've covered that adequately on this thread I
think - I like the Build->Batch.. approach a lot)
2. Make a directory to be the root of your installation (e.g.
E:\Python-2.2.2)
3. Into this directory, copy over PC\*.ico and PCbuild\*.exe
4. Create E:\Python-2.2.2\DLLs and copy over PCBuild\*.pyd
5. Copy the Include tree into E:\Python-2.2.2. Also copy PC\pyconfig.h into
Include
6. Copy the Lib tree into E:\Python-2.2.2
7. Create E:\Python-2.2.2\libs and copy over PCbuild\*.lib
8. Copy PCbuild\*.dll to C:\WINNT\system32
9. Add E:\Python-2.2.2 to the Path (Control Panel -> System -> Advanced ->
Environment Variables)

Once I did this, I could get a debug installation of wxPython installed
relatively easily and it all looks like it works.

But, as always, your milage may vary.

Thanks for all the help guys,

S.