This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jcea
Recipients PeterL, jcea
Date 2010-04-24.13:16:26
SpamBayes Score 1.3194137e-09
Marked as misclassified No
Message-id <1272114990.85.0.637201781745.issue8516@psf.upfronthosting.co.za>
In-reply-to
Content
Please, install Berkeley DB 4.6.X in linux and reinstall bsddb3 to use it, instead of BDB 4.7. Would be a good idea to install pybsddb 4.7.3, too, to mimic Windows environment under linux closely.

After doing this, and verifying that linux resemble now the Windows environment, try the DB load again.

I need to confirm if the issue is in bsddb module, Berkeley DB code or BDB interaction with Windows OS/Filesystem.

Anyway, if installing a modern bsddb3 (note that we have 5.0.0 available) makes the problem go away, it is a non-issue. Python 2.6 is basically in security/crashes fixes only now. Or very close to it.

With python 2.7 almost ready, I would try the beta too, to confirm this problem is not a problem anymore.
History
Date User Action Args
2010-04-24 13:16:30jceasetrecipients: + jcea, PeterL
2010-04-24 13:16:30jceasetmessageid: <1272114990.85.0.637201781745.issue8516@psf.upfronthosting.co.za>
2010-04-24 13:16:28jcealinkissue8516 messages
2010-04-24 13:16:26jceacreate