➜

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 r.david.murray
Recipients aleax, lehmannro, loewis, r.david.murray, zhigang
Date 2010-02-11.03:32:38
SpamBayes Score 1.9467281e-08
Marked as misclassified No
Message-id <1265859164.42.0.56618196441.issue5483@psf.upfronthosting.co.za>
In-reply-to
Content 
I agree that caching for speed is something that should be implemented in another layer.  It certainly is orthogonal to the writeback issue.  The best caching strategy is going to depend on the application, so I don't think caching for speed belongs in Shelve itself.  Closing as rejected.
History
Date User Action Args
2010-02-11 03:32:44r.david.murraysetrecipients: + r.david.murray, loewis, aleax, lehmannro, zhigang
2010-02-11 03:32:44r.david.murraysetmessageid: <1265859164.42.0.56618196441.issue5483@psf.upfronthosting.co.za>
2010-02-11 03:32:38r.david.murraylinkissue5483 messages
2010-02-11 03:32:38r.david.murraycreate