dbus-python 0.80rc1 release candidate

[John (J5) Palmieri]

On Thu, 2006-12-07 at 18:51 -0500, John (J5) Palmieri wrote:
> On Thu, 2006-12-07 at 18:06 -0500, John (J5) Palmieri wrote:
> > On Thu, 2006-12-07 at 17:04 -0500, John (J5) Palmieri wrote:
> > > On Wed, 2006-12-06 at 14:50 +0000, Simon McVittie wrote:
> > > > Release candidate 1 for dbus-python 0.80 is now available. Please
> > > > download, test, try to break it.
> > > > 
> > > 
> > > Still tracking it down but sugar no longer starts.  We are getting a
> > > connection != NULL assertion when calling
> > > dbus_connection_send_with_reply.  Unfortunately it happens in the
> > > library so I don't have a python traceback.  0.80pre1 ran sugar a bit
> > > better so perhaps you might have insight into the issue based on the
> > > changes you made. I'll look more in depth and post anything I find.
> > 
> > 
> > A little more info.  In pdb I am segfaulting in the second call to
> > dbus.SessionBus().  This is really weird.  If I don't step through and
> > just hit continue I get AttributeError: 'PresenceService' object has not
> > attribute 'get_object'
> 
> That AttributeError is wrong and most likely due to the stack being
> trashed somewhere in the bindings.  We are calling get_object on the bus
> right after the 2nd bus = dbus.SessionBus() call.  That is the call that
> crashes in pdb if I step through.

Ok, cleaning out the dbus module (rm -rf ;) and then installing gives me
a better backtrace.  I think the crash was from competing installs. 

Now I get:

File "/usr/lib/python2.4/site-packages/dbus/__init__.py", line 177 in ?
  from _dbus_bindings import get_default_main_loop,
set_default_main_loop,\
ImportError: cannot import name get_default_mail_loop

 
-- 
John (J5) Palmieri <johnp at redhat.com>