Message233499
| Author |
krichter |
| Recipients |
docs@python, krichter, r.david.murray |
| Date |
2015年01月06日.01:58:54 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1420509535.46.0.30738907687.issue23174@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Then, let the error message say "You are opening a just-created empty file. The db type of the file cannot, therefore, be determined." which is much clearer than "anydbm.error: db type could not be determined" which sounds like a generic fallback error message in "an error occured"-style.
It seems to be necessary that the filename passed to `shelve.open` has a suffix which is not very intuitive for Linux users. It'd be great to have validation of the suffix and raise a `ValueError` with an error message like `"filename '%s' doesn't contain a suffix" % (filename,)` when it isn't supplied. If there's another issue regarding the fact that the file is "just-created" and empty, this is independent of the issue above. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年01月06日 01:58:55 | krichter | set | recipients:
+ krichter, r.david.murray, docs@python |
| 2015年01月06日 01:58:55 | krichter | set | messageid: <1420509535.46.0.30738907687.issue23174@psf.upfronthosting.co.za> |
| 2015年01月06日 01:58:55 | krichter | link | issue23174 messages |
| 2015年01月06日 01:58:54 | krichter | create |
|