RE: [wxPython] wxc module when running debug
Ok, hugely helpful. One more question: So far I’ve been
able to just use the standard wxPython binary distribution
and haven’t had to do a local build of either wxWindows or
wxPython. This is very nice from my perspective and I would
prefer to continue on that way. Is there, or will there be
with the next release, a binary distribution for windows
that will include the debug versions of the pyds/dlls?
···
-----Original Message-----
From: Robin Dunn [mailto:robin@alldunn.com]
Sent: Tuesday, August 06, 2002 3:53 PM
To: wxpython-users@lists.wxwindows.org
Subject: Re: [wxPython] wxc module when running debug
Sorry to belabor this, but it is fairly critical to our
use of Python and wxPython:
- Why do I not need the *_d.pyd files for the regular
Python libraries?
It’s just the way Python works. When Python itself is built in debugging
mode on win32 it will look for modulename_d.pyd (and *_d.dll too BTW) and
not modulename.pyd. The nondebug build of Python works the other way
around.
- Is the byte-code between debug and non-debug versions
different?
No, but .pyd files are not byte-code.
- How do you create the .pyd files?
They are DLLs that happen to have a .pyd filename extension. (BTW, Python
will also search for modulename.dll or modulename_d.dll when doing an import
statement.)
- Would I need these debug versions for every wxPython
script?
No, only the binary extension modules and only when you are running the
debug version of the interpreter.
–
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
wxpython-users mailing list