[ZODB-Dev] StandaloneZODB release: when?

[Andrew Kuchling]

On Wed, Nov 14, 2001 at 05:59:46PM -0500, Barry A. Warsaw wrote:
>- documentation ;)

What's missing?  READMEs, docstrings, a manual, what?  If the latter,
I'll happily contribute the source code for the ZODB guide.
(Docstrings aren't a bad idea, now that I think of it; right now
"pydoc ZODB" doesn't get you anything very helpful.)

>- integrating Greg's ConflictError patch

Agreed.  It's an obvious cleanup.  Neil, do you think your zeod
cleanup could go in, or is it too radical?

>- integrating the contributions, e.g. PersistentList

I'd consider them optional, at least for a 1.0 release, because IMHO
more discussion is needed on what should be integrated and how it
should be done.  See, I'd like to make it falling-off-a-log easy to
use ZODB as a data store in Python programs, and it's not quite there
yet.  It's almost there if you don't need concurrent access
(concurrent access drags in ZEO and the necessity for a running server
process), but I suspect anyone using the ZODB seriously would end up
writing tools similar to opendb and zodb_census, and we should try to
save users from reinventing the wheel.

>I'd definitely like to keep it alive for the bug and patch tracking!

OK, that's easily left alone.  (In fact it's not clear to me that you
can withdraw a SourceForge project, which is unfortunate.)

--amk