On Tue, Jul 09, 2013 at 08:35:54AM +0100, Gordon Sim wrote:
> On 07/08/2013 04:34 PM, Darryl L. Pierce wrote:
> >Has anybody hit an issue with running the Python swig bindings on Qpid?
> >I'm getting a segfault and have tracked it down to the following piece
> >in swig_python_typedefs.i:
> >
> >%init %{
> >   /* Instead of directly referencing the uuid module (which is not
> >  * available
> >    * on older versions of Python), reference the wrapper defined in
> >    * qpid.datatypes.
> >    */
> >   pUuidModule = PyImport_ImportModule("qpid.datatypes");
> >
> >   /* Although it is not required, we'll publish the uuid module in our
> >    * module, as if this module was a python module and we called
> >    * "import uuid"
> >    */
> >   Py_INCREF(pUuidModule);
> >   PyModule_AddObject(m, "uuid", pUuidModule);
> >%}
> 
> I get a segfault if the qpid.datatypes is not on the PYTHONPATH.
> Otherwise not.

Hrm, is that package a requirement for the Swigged bindings rather than
the pure Python bindings?

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/

Attachment: pgpv3rYoXj0ku.pgp
Description: PGP signature

Reply via email to