Message235527
| 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:17 | krichter | set | recipients:
+ krichter, r.david.murray, docs@python |
| 2015年02月07日 13:58:17 | krichter | set | messageid: <1423317497.47.0.61265471169.issue23174@psf.upfronthosting.co.za> |
| 2015年02月07日 13:58:17 | krichter | link | issue23174 messages |
| 2015年02月07日 13:58:16 | krichter | create |
|