Re: [Duplicity-talk] "ImportError: No module named GnuPGInterface" with 0.4.3.RC8

[Kenneth Loafman]

Nick Burch wrote:
> On Tue, 3 Jul 2007, Kenneth Loafman wrote:
>> Yes, its part of the python-gnupginterface module.  I need to set that
>> up as a requirement for the duplicity package.
> 
> Ah, right. If anyone else is searching for a srpm for this, I've found
> the following one:
> http://www.python.org/pyvault/SRPMS/repodata/repoview/python-gnupginterface-0-0.3.2-3.html

Thanks for the pointer.

> With python-gnupginterface installed, I can run 0.4.3-RC8 just fine on
> RHEL 4 (python 2.3.4). However, when I try it on RHEL 3 (python 2.2.3),
> I get a nasty exception:
> 
> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 30, in ?
>     from duplicity import collections, commandline, diffdir, dup_temp, \
>   File
> "/var/tmp/duplicity-0.4.3.RC8-0.fdr.6-root-root/usr/lib/python2.2/site-packages/duplicity/commandline.py",
> line 22, in ?
>   File
> "/var/tmp/duplicity-0.4.3.RC8-0.fdr.6-root-root/usr/lib/python2.2/site-packages/duplicity/backends.py",
> line 27, in ?
> AttributeError: 'module' object has no attribute 'setdefaulttimeout'
> 
> 
> That seems to correspond to:
>     # TODO: move into globals?
>     socket.setdefaulttimeout(10)
> 
> It looks like python 2.2 doesn't have a setdefaulttimeout on its socket.
> I guess we'll want something like this instead:
>     # TODO: move into globals?
>     if hasattr(socket,"setdefaulttimeout"):
>             socket.setdefaulttimeout(10)

Let me know if that works or if you have other problems with 2.2.

I know we do now, but going forward I'm not sure we want to support 2.2
any more.  Python 2.2 is quite ancient and once we get past the current
problem, may cause other problems, or keep us from advancing due to lack
of features like this.  However, until that happens, I'll apply the fix
you supplied and hope for the best.

...Thanks,
...Ken