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 krichter
Recipients docs@python, krichter, r.david.murray
Date 2015-02-07.13:58:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423317497.47.0.61265471169.issue23174@psf.upfronthosting.co.za>
In-reply-to
Content
After checking the code, I think that it'd make more sense to document `whichdb.py`. It needs to be enhanced with references to criteria for the determination of the database type. Currently there're only function comments and the fact that some variables are named magic speaks for itself, i.e. it's ok for the implementation of the module to be a black box, but the requirements for the input, i.e. the potential database file, which is per se not part of the black box, needs to be specified. Then just link that in the `shelve` docs stating that `shelve.open` is basically a wrapper around `whichdb`.
History
Date User Action Args
2015-02-07 13:58:17krichtersetrecipients: + krichter, r.david.murray, docs@python
2015-02-07 13:58:17krichtersetmessageid: <1423317497.47.0.61265471169.issue23174@psf.upfronthosting.co.za>
2015-02-07 13:58:17krichterlinkissue23174 messages
2015-02-07 13:58:16krichtercreate