I would like this idea fine if we were not still running
most of our sites on 2.4.  It will still be a while before we
are ready to leave 2.4 behind.

It seems we could guard against this particular problem by adding
something to the durus/__init__.py
It does seem odd, though, to write code to detect broken installations,

On Jun 28, 2010, at 6:41 PM, Michael Watkins wrote:

> On Mon, June 28, 2010 14:48, Neil Schemenauer wrote:
>> Ah, implicit relative import bites us.  I wonder if it would be time
>> to switch to using absolute imports.  i.e, add
>>
>>    from  __future__ import absolute_import
>>
>> to the Durus modules.  That would make Durus depend on Python 2.5.
>
> Never having once used relative imports in all these years, +1 from me.
> Running 2.6.x and 3.1.x or higher these days.