On Tue, Jul 09, 2013 at 10:34:23AM -0400, Darryl L. Pierce wrote:
> On Tue, Jul 09, 2013 at 03:08:44PM +0100, Gordon Sim wrote:
> > >Ah, kk, I follow. Hrm, the inclusion causes Python 2.7.3 and 2.7.5 to
> > >segfault (I first hit this issue before upgrading to F19).
> >
> > Even with qpid.datatype
On Tue, Jul 09, 2013 at 03:08:44PM +0100, Gordon Sim wrote:
> >Ah, kk, I follow. Hrm, the inclusion causes Python 2.7.3 and 2.7.5 to
> >segfault (I first hit this issue before upgrading to F19).
>
> Even with qpid.datatypes on the path?
Yep. I just verified that it blows up.
--
Darryl L. Pierce
On 07/09/2013 03:00 PM, Darryl L. Pierce wrote:
On Tue, Jul 09, 2013 at 02:37:42PM +0100, Gordon Sim wrote:
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?
Yes, i
On Tue, Jul 09, 2013 at 02:37:42PM +0100, Gordon Sim wrote:
> 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?
> >>
> >>Yes, its actually not re
On 07/09/2013 02:34 PM, Darryl L. Pierce wrote:
On Tue, Jul 09, 2013 at 02:10:20PM +0100, Gordon Sim wrote:
On 07/09/2013 01:53 PM, Darryl L. Pierce wrote:
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
On Tue, Jul 09, 2013 at 02:10:20PM +0100, Gordon Sim wrote:
> On 07/09/2013 01:53 PM, Darryl L. Pierce wrote:
> >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 Qpi
On 07/09/2013 01:53 PM, Darryl L. Pierce wrote:
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 pi
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:
> >
> >%in
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
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), refe
10 matches
Mail list logo
