[issue5754] Shelve module writeback parameter does not act as advertised

2010-02-10 Thread R. David Murray
R. David Murray added the comment: Thanks for the patch. I applied the doc patch and a slightly simplified version of the test in r78141 (we tend to just let errors bubble up rather than code explicit Fails, since as often as not if you provide a specific message it turns out to be wrong whe

[issue5754] Shelve module writeback parameter does not act as advertised

2009-09-17 Thread Robert Lehmann
Robert Lehmann added the comment: I think you're misquoting Python's shelve module documentation in your first sentence. The documentation says: "By default modified objects are written only when assigned to the shelf [...]. If the optional writeback parameter is set to True, all entries accesse

[issue5754] Shelve module writeback parameter does not act as advertised

2009-04-21 Thread Daniel Diniz
Changes by Daniel Diniz : -- keywords: +easy stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue5754] Shelve module writeback parameter does not act as advertised

2009-04-14 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> aleax nosy: +aleax ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue5754] Shelve module writeback parameter does not act as advertised

2009-04-14 Thread Jorge Herskovic
New submission from Jorge Herskovic : The shelve module documentation states that "by default, mutations to persistent-dictionary mutable entries are not automatically written back. If the optional writeback parameter is set to True, all entries accessed are cached in memory, and written back at