Concurrency and shelve

[Erno Kuusela]

In article <3AA26D5E.2FD28B40 at stroeder.com>, Michael Ströder
<michael at stroeder.com> writes:

| HI!
| Can anybody summarize issues with shelve (based on anydbm) and
| concurrent access? I experienced with bsddb that changes to the DB
| within one instance are only visible after calling close() to a
| second instance of the same database.

it depends on the dbm implementation that anydbm happens to
pick up. afaik only gdbm does locking, the others break.
if you look in the shelve module, it is easy to see how to
make it use gdbm if you want. the classes there are not
documented however so it may not be safe to rely on them being there.

  -- erno