Alain, I can not reproduce this issue in current bsddb code (as running
under Python 2.6.1 and Berkeley DB 4.7.25). Since Python 2.5 branch has
been marked as "security fixes only", this bug would be an "out of date"
one.

Please, confirm that this bug is not present in Python 2.6.1 or, if you
need to run Python 2.5, please install an updated pybsddb library and
check it.

I will wait your comments for a week or two. Then mark this issue as
"out of date", if you don't indicate the contrary.

Thanks for your time.