>>> Given that we haven't been able to solve the bsddb
>>> corruption/run-recovery problem,
>> 
>> I've completely given up and am happy in my ZODB.FileStorage world
>> <0.1 wink>.  I'd like to include the necessary ZODB stuff in a a1
>> build so that people can give ZODB a go if they would like, assuming
>> that it doesn't bloat the installer too much.
> 
> I played around a little with a SQLite classifier also, which is very
> lightweight to install.  It was pretty slow when working with the 2.8
> version because of the way we do our commits, but I'd like to give it
> another go with the 3.0 version of SQLite to see if the situation has
> improved.  Maybe I can get this in for 1.1a2 so that it could get some
> testing.  Right now, I don't know if it would really be any more
> stable than bsd or not.

Hope you don't mind (I don't know if you already knew if or applies)
but are you aware that the Subversion core dev team currently advise
against the use of bsddb 4.1 versions?  They recomend either 4.0 or 4.2.
http://www.subversion.org/faq.html#bdb41-tabletype-bug

In Python 2.3.4 (that's what I've got installed):

  >>> import bsddb
  >>> bsddb._db.version()
  (4, 1, 25)
  >>> bsddb._db.DB_VERSION_STRING
  'Sleepycat Software: Berkeley DB 4.1.25: (December 19, 2002)'
  >>> 

BTW, Sorry for my comments about MSVCR71.DLL.  I've just seen
(in other mailing lists) that you knew all the points I raised
in my previous emails.

Regards,
-H.

_______________________________________________
spambayes-dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/spambayes-dev

Reply via email to