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 Claudiu.Popa, r.david.murray, rhettinger, serhiy.storchaka
Date 2014-06-24.21:03:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403643821.85.0.540551723842.issue21708@psf.upfronthosting.co.za>
In-reply-to
Content
The point is to make the API consistent.  So if the other dbm modules raise an error when __setitem__/__delitem__ are called on an R/O db, then the warnings are appropriate (but should mention that this will be an error in the future).

The warnings will only be printed once per run of python, unless I'm completely misremembering how deprecation warnings work.
History
Date User Action Args
2014-06-24 21:03:41r.david.murraysetrecipients: + r.david.murray, rhettinger, Claudiu.Popa, serhiy.storchaka
2014-06-24 21:03:41r.david.murraysetmessageid: <1403643821.85.0.540551723842.issue21708@psf.upfronthosting.co.za>
2014-06-24 21:03:41r.david.murraylinkissue21708 messages
2014-06-24 21:03:41r.david.murraycreate