Debuggin a ptyhon extension

[Roger Upole]

It's probably looking for the debug version of win32api
(win32api_d.pyd, which will also require a debug build of
Pywintypes).  You can grab the pywin32 source and
roll your own debug binaries, or alternately you might
be able to get away with creating a release build of Python
that contains debug info.
  hth
     Roger

"Steve Menard" <devilwolf22 at hotmail.com> wrote in message
news:rzxmc.26524$j11.254148 at weber.videotron.net...
> I am writing a python extension module in VC++ on windows. At some
> point, my extension crashes.
>
> Now I want to debug exactly why. I built the python projects in VC++,
> and put the resulting python_d.exe in my ptyon home directory, and the
> python23_d.dll in the windows/system32 directory. I also tried to put
> the python23_d.dll in python's home directory, to the same result.
>
> Problem is, running my scripts/extension with python_d.exe, it always
> complains it can't find win32api. Yes, I am using win32API to preload a
> dll, and can't really get rid of it.
>
> To try and solve this, I tried replacing the "stock" python.dll with my
> python_d, so at least VC++'s debugger would see the debug info. but I
> got the same result, of win32api not being found ...
>
> What is the best way to go about this? My extension will require a fair
> amount of native code and interacting with the Python code, so being
> able to trace into python would be invaluable.
>
> Are my problems caused because python 2.3.3 (and possible win32all) were
> build using VC.net?
>
> I am grateful for any help you guys can provide.
>
>
> Steve Menard
> devilwol22 at hotmail.com
>