gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Glupy bugs: found the solution?


From: Justin Clift
Subject: Re: [Gluster-devel] Glupy bugs: found the solution?
Date: Sat, 26 Oct 2013 18:57:07 +0100

On Sat, 26 Oct 2013 17:47:17 +0200
Niels de Vos <address@hidden> wrote:
<snip>
> > I haven't used Pdb before, instead I'm using PyCharm (an IDE).  I need
> > to figure out how to get the debugger in that working with Glupy
> > translators so I can find out what's being called from where.

Been trying this out for a few hours while on the train back from
Edinburgh (Linuxcon Europe), without success.  Kind of suspecting
I'll need to learn pdb soon. :(

It's kind of weird, as I'm pretty sure I *used* to have this working
with an older version of PyCharm (2.7.x).  The new 3.0 version of
PyCharm is just giving me SEGFAULT and SIGABRT when I try to get a
Gluster translator working with it (frustrating).

/me will keep trying different things for a bit


> > Kind of suspecting it might be the libgfapi stuff (not Swift)
> > getting picked up on my system instead of Glupy.  But really,
> 
> That is correct. Recent glusterfs-api RPMs provide 
> /usr/lib/python2.6/site-packages/gluster/gfapi.py so that a future swift 
> implementation can use that. It is also trivial to write your own Python 
> script that imports gluster.gfapi and accesses volumes through libgfapi.  
> See slide 10 from 
> http://people.redhat.com/ndevos/talks/Gluster-Stockholm-20130902.pdf for 
> a minimal example.

Yeah, that's why I was thinking it was libgfapi stuff getting pulled in
not Swift.  The import line in your pdf needs updating btw, as the
import line for current git head needs to be:

  from gluster import gfapi


<snip>
> the Python package 'gluster' will be the base for other modules. Hence 
> we have created put the api bindings in gluster/gfapi.py. I think it 
> would make sense to rename the Glupy module gluster.glupy. If it can be 
> placed in /usr/lib/python2.6/site-packages/gluster/glupy.py things would 
> be even nicer :)

That would make the import line:

  from gluster import glupy

Wouldn't it?  No objections to that, it's fairly simple and pretty logical. :)

+ Justin

-- 
Justin Clift <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]