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 MLModel
Recipients MLModel, georg.brandl
Date 2009-05-07.18:00:38
SpamBayes Score 0.0032060528
Marked as misclassified No
Message-id <1241719241.22.0.336086356581.issue5957@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation of shelve.open() states (paragraph 3) that "By
default, mutations to persistent-dictionary mutable entries are not
automatically written back." It then goes on to describe what happens if
the writeback parameter is True, which involves caching the entire
dictionary of objects in memory and writing the whole thing back on close.

But what happens if writeback is False, the default? The statement that
the mutable entires are not automatically written back leaves open the
question of how to write them back. shelf.sync() is documented as being
used only when writeback is true. Also, for a user unfamiliar with the
nuances of persistence the sentence quoted above is somewhat mysterious
-- "persistent-dictionary mutable entries"? "written back"?
History
Date User Action Args
2009-05-07 18:00:41MLModelsetrecipients: + MLModel, georg.brandl
2009-05-07 18:00:41MLModelsetmessageid: <1241719241.22.0.336086356581.issue5957@psf.upfronthosting.co.za>
2009-05-07 18:00:39MLModellinkissue5957 messages
2009-05-07 18:00:38MLModelcreate