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 Jim.Jewett
Recipients Arfrever, Claudiu.Popa, Jim.Jewett, ncoghlan, serhiy.storchaka
Date 2014-04-23.22:38:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398292687.67.0.277060879195.issue19385@psf.upfronthosting.co.za>
In-reply-to
Content
I think the requested timing regression was for the non-broken case.  When the database has NOT been closed, and keys() still works, will it be way slower than before?

Note that I am not asking you to do that test (though the eventual committer might); the implementation of whichdb leaves me believing that almost anyone who is likely to care will have already followed the docunmentation's recommendation to install another *dbm ahead of dumb.
History
Date User Action Args
2014-04-23 22:38:07Jim.Jewettsetrecipients: + Jim.Jewett, ncoghlan, Arfrever, Claudiu.Popa, serhiy.storchaka
2014-04-23 22:38:07Jim.Jewettsetmessageid: <1398292687.67.0.277060879195.issue19385@psf.upfronthosting.co.za>
2014-04-23 22:38:07Jim.Jewettlinkissue19385 messages
2014-04-23 22:38:07Jim.Jewettcreate