After diving deeper into boost.python and python than I felt comfortable
with, I found my own stupid mistake.
On Windows, the presence of _DEBUG causes Py_DEBUG to be defined, but
this is not the case on Linux. When I include boost/python.hpp I need to
define both BOOST_DEBUG_PYTHON and Py_DEBUG:
Brian O'Kennedy wrote:
After diving deeper into boost.python and python than I felt comfortable
with, I found my own stupid mistake.
On Windows, the presence of _DEBUG causes Py_DEBUG to be defined, but
this is not the case on Linux. When I include boost/python.hpp I need to
define both BOOST_
I think the configure step on linux generates the pyconfig.h file which
contains
#define Py_DEBUG 1
On Windows, the pyconfig.h file comes from Python/PCBuild/pyconfig.h
which seems to be hand generated and contains:
#ifdef _DEBUG
# define Py_DEBUG
#endif
I suppose the reason this was don
Hi guys,
I found a problems with my binds when I work with separated modules.
In my function where return a c++ pointer to a object, this not return
the same python object used in setter function.
The main point here is because this works fine when all classes are
exported in the same module but w
Is this a confirmed bug?
Thanks,
Josh
-Original Message-
From: cplusplus-sig-bounces+josh.davidson=lmco@python.org
[mailto:cplusplus-sig-bounces+josh.davidson=lmco@python.org] On Behalf Of
Davidson, Josh
Sent: Thursday, April 16, 2009 10:04 AM
To: Development of Python/C++ integ
Stefan Seefeld wrote:
Robin Gilks wrote:
A difficult question to put a title to so I'll paint a brief scenario...
The application is written in c++
It receives a data message and instantiates a message decoder class.
Based on the contends that are extracted into the class variables, a
respons
