Hi Robin & All,
Andrea Gavana wrote:
I used bsddb because it allows me to save
and load a Python class very easily, and it only requires a sync() and
close() method to work.It's really sad that this is happening, both since PyBSDDB was once my
foster-child, but also because it is so dang powerful considering its
relative simple API. The current maintainer of the package is using it with
a distributed data storage system (IOW, spread across multiple servers that
are not sharing disks) that totals over 200 terabytes of storage and has
about 2**35 objects stored within it. So although Python is taking several
steps forward with 3.0, removing this package from the core distribution
seems like one step back to me.
I perfectly agree. I can't really get the reasoning of the developers
on python-dev, but then, I am just a little programmer with no voice
in the great Python community. In any case, should I do the switch now
or keep using bsddb anyway, even if in the future it will be a
separate download and it will not live in the standard library? What
do wxPython-users think? I am not going to use sqlite, not in a
thousand years. It is a db-disgrace, and it's a pity SQLAlchemy is not
in the standard lib. I'll probably follow Chris' suggestion a use a
simple cPickle to save data to the new-format database.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
···
On Mon, Sep 15, 2008 at 11:28 PM, Robin Dunn wrote: