I think I saw over on the qwitter list that this occurred because
someone had a durus installation directory inside a durus installation
directory at the time that the root was instantiated,
I'm not sure what the installation method was, but the results
were bad.

On Jun 28, 2010, at 3:56 PM, Neil Schemenauer wrote:

> Binger David  wrote:
>>
>> On Jun 25, 2010, at 4:30 PM, Alex Hall wrote:
>>> Repr(data): '\x80\x02cdurus.durus.persistent_dict\nPersistentDict\nq\x01.x\x
9c\xb5Z}`\\E\x11O\x8e\x92\xa6I\x9a\xb6iB\xcbw
>>>
>>> ...
>>
>> The string should start with
'\x80\x02cdurus.persistent_dict\nPersistentDict\nq'
>> not
>> '\x80\x02cdurus.durus.persistent_dict\nPersistentDict\nq'.
>>
>> I think this is the problem.  I'm not sure how it originates.
>
> Definitely a problem.  I wonder if somewhere the Connection class
> got passed a bad 'root_class' argument.  I can't see any way Durus
> itself can create such a thing.
>
> As a hack so you can load your data, add this early in the startup
> (e.g. before Durus is imported):
>
>    import sys
>    import durus
>    durus.durus = durus
>    sys.modules['durus.durus'] = durus
>
> After that you should be able to execute:
>
>    import durus.durus.persistent_dict
>
> without errors.
>
> Regards,
>
>  Neil
>
> _______________________________________________
> Durus-users mailing list
> Durus-users@mems-exchange.org
> http://mail.mems-exchange.org/mailman/listinfo/durus-users