On 31/07/12 22:58, Jim Bosch wrote:
On 07/31/2012 06:14 PM, Glenn Ramsey wrote:
Using boost::python how can I create an a custom exception that is
derived from Python's Exception? The functionality I would like to get
by doing this is to provide additional methods for the catching co
On 31/07/12 21:14, Glenn Ramsey wrote:
Using boost::python how can I create an a custom exception that is derived from
Python's Exception? The functionality I would like to get by doing this is to
provide additional methods for the catching code to retrieve information from
the exceptio
Using boost::python how can I create an a custom exception that is derived from
Python's Exception? The functionality I would like to get by doing this is to
provide additional methods for the catching code to retrieve information from
the exception.
I know it is possible to just wrap and th
On 07/10/11 09:36, Glenn Ramsey wrote:
Is it possible to pass an opaque pointer from one bpl module to another?
Following the documentation [1] I am able to successfully pass an opaque pointer
from one function in a module to another function in that same module.
Attempting to pass the opaque
Is it possible to pass an opaque pointer from one bpl module to another?
Following the documentation [1] I am able to successfully pass an opaque pointer
from one function in a module to another function in that same module.
Attempting to pass the opaque pointer to another module results in an
When making a debug build (using MSVC on Windows) of an extension module using
Boost.Python it is possible to link with a release build of pythonXX.lib.
However this appears to not be possible for modules wrapped using SIP or SWIG
E.g. [1].
How does Boost.Python do this?
The reason I ask is t
