Undefined calling conventions in Python.h

Fredrik Lundh fredrik at pythonware.com
Wed Jul 23 14:02:24 CEST 2008

Jaco Naude wrote:

> That said, let me double check something which might be causing
> problems since you will be familiar with this. Which Python.h file do
> you include when including the DLL in your programs? The one in the
> source distribution of the one in the installation distribution? I've
> been including the one in the installation distribution all along.
> When I try to include the one in the source distribution it gets up to
> the point where it looks for the following include:
> #include "pyconfig.h"
> This file is not in the same directory as the Python.h file in the
> source distribution. Because of this I just used Python.h in the
> installation distribution.

that's just two copies of the same file, as far as I know.

the "pyconfig.h" file contains platform-specific information; it's 
generated from pyconfig.h.in on Unix-style systems, and copied from the 
PC directory on Windows.


More information about the Python-list mailing list