Guido> I think I've seen this too when running the bsddb3 unittest. I
Guido> think it's caused by a previous test ending badly and leaving
Guido> junk behind that the test suite doesn't properly remove before
Guido> starting. But I don't recall the details.
skip> Thanks, that
Guido> I think I've seen this too when running the bsddb3 unittest. I
Guido> think it's caused by a previous test ending badly and leaving
Guido> junk behind that the test suite doesn't properly remove before
Guido> starting. But I don't recall the details.
Thanks, that at least g
I think I've seen this too when running the bsddb3 unittest. I think
it's caused by a previous test ending badly and leaving junk behind
that the test suite doesn't properly remove before starting. But I
don't recall the details.
--Guido
On Dec 5, 2007 5:24 PM, Gregory P. Smith <[EMAIL PROTECTED]
I'd expect 4.5 to work fine but I don't know why you're getting such a
strange error, i've never seen that. fwiw i suggest people avoid
berkeleydb 4.6 for now.
On 12/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I noticed that test_anydbm and test_bsddb seemed to hang, so I -x'd them.
>
I noticed that test_anydbm and test_bsddb seemed to hang, so I -x'd them.
Later on while test_whichdb was running and I was off doing something else
(so didn't notice the delay), it eventually spewed this traceback:
Traceback (most recent call last):
File "/Users/skip/src/python/trunk/L
