Using Exception instead of glib seems reasonable. Could you try the solution here for the warnings issue: http://stackoverflow.com/questions/2059675/catching-warnings-pre-python-2-6 Works fine, here is the code from torrentview.py: original_filters = warnings.filters[:] #Supress Warning: g_object_s...

If I put the from __future__ import with_statement at the very top before all other imports, then no error. Oh well, it causes problems, for instance with treefilterview.py line 263, at pix = model.get_value(row, 4) I get object has no attribute 'catch_warnings', and the filter tree view has all it...

Can you try putting the following before the statement: from __future__ import with_statement with warnings.catch_warnings(): warnings.simplefilter("ignore") I get this error if I try that: File "/usr/lib/python2.5/site-packages/deluge-1.3.3-py2.5.egg/deluge/ui/gtkui/torrentview.py&q...

Removing that try-except will cause deluge to crash if there is a problem with images at that point. Adding a try-except around the import glib would be a workaround but if this is isolated to lenny seems a bit pointless. That's what the code was in 1.31, the try except with glib was added in 1.32 ...

Problem with leaving in the try: gtk.gdk.pixbuf_new_from_file, is the glib.Gerror which requires the import glib which I don't have.

I do have python-gobject installed, but that doesn't seem to provide glib bindings in Lenny.

I'm stuck with Lenny, and upgrading to Python later than 2.5 is a HUGE pain since all the packages have to be recompiled. I started down that path, and gave up. Instead I dug into Deluge 1.33 to see why it needed a Python newer than 2.5. The changes seemed minor, so I wonder why support for Python 2...