RE: [wxPython] wxc module when running debug
Hm. I’m confused. I do have a file called “wxc.pyd” or
do you mean that I also need “wxc_d.pyd”?
···
-----Original Message-----
From: Robin Dunn [mailto:robin@alldunn.com]
Sent: Tuesday, August 06, 2002 12:33 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxc module when running debug
I’ve got an application with an embedded Python interpreter that
uses wxPython. When linking and running non-debug everything
works fine. However, when linking in debug and running the app
Python cannot find the module “wxc”. Looking in the wxPython
stuff in site-packages I see a wxc.pyd. Has anyone else run
into this?
When Python is built in debug mode on Win32 then it requires that all
extension modules have the _d (ex. wxc_pyd) in the name, just like the
python dll. I think this is done so both can coesist and also because they
each link to different CRT libs.
I remember seeing a message in comp.lang.python that described a one line
hack to Python that changes this behaviour, but I don’t remember what it is.
The other soultion is to build your own debug version of wxPython, so you
get the *_d.pyd’s that you need.
–
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
wxpython-users mailing list