On Jan 14, 11:48 am, Graham Dumpleton
wrote:
> As a test, just prior to where unpickle is done, do:
>
> import sys
> import d4
>
> print >> sys.stderr, "d4.__name__", dr.__name__
> print >> sys.stderr, "d4.__file__", dr.__file__
>
> This will just confirm that manual import works and what
On Jan 14, 9:41 pm, Ståle Undheim wrote:
> On Jan 14, 11:31 am, Graham Dumpleton
> wrote:
>
>
>
> > On Jan 14, 9:20 pm, Ståle Undheim wrote:
>
> > > I have a pretty strange error that I can't figure out the cause off.
> > > This is in a Django app.
>
> > > I am using berkelydb, with secondary da
On Jan 14, 11:31 am, Graham Dumpleton
wrote:
> On Jan 14, 9:20 pm, Ståle Undheim wrote:
>
>
>
> > I have a pretty strange error that I can't figure out the cause off.
> > This is in a Django app.
>
> > I am using berkelydb, with secondary databases for indexing. The
> > secondary databases are as
On Jan 14, 9:20 pm, Ståle Undheim wrote:
> I have a pretty strange error that I can't figure out the cause off.
> This is in a Django app.
>
> I am using berkelydb, with secondary databases for indexing. The
> secondary databases are associated with a callback that uses cPickle
> to serialize inde
I have a pretty strange error that I can't figure out the cause off.
This is in a Django app.
I am using berkelydb, with secondary databases for indexing. The
secondary databases are associated with a callback that uses cPickle
to serialize index values. The problem is that cPickle.dumps(value)
fa
