Undefined calling conventions in Python.h

Fredrik Lundh fredrik at pythonware.com
Wed Jul 23 14:35:11 CEST 2008

Jaco Naude wrote:

> Fredrik, thanks for the help. I'm not sure why but it seems to work
> now even if I don't include the extern "C" command. It also works with
> both Python.h files (after I copied pyconfig.h from the PC folder). So
> it seems like everything is working now.

As it's supposed to do.  It's times like this that you really want to 
use a system that takes snapshots of every single revision of the files 
you work on, so you can see what exactly it was you had done when it 
didn't work (it's more often a "do'h" thing than a heisenbug ;-).

(fwiw, I'm currently trying to track down a problem at a customer site 
when the entire Python application managed to remove itself during a 
test run; the program crashed with "zipimport: IOError" when they tried 
to use a part of the system that did some lazy imports, and when they 
tried to restart the program, neither the startup script nor the ZIP 
archive that contained the bulk of the application were anywhere to be 
seen.  Other PY files in the same directory were left intact.  Fully 
patched Windows XP, clean bill of health from a virus scanner.  If 
anyone's ever experienced anything similar, let me know.)


More information about the Python-list mailing list