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 Sworddragon
Recipients Sworddragon, docs@python
Date 2013-11-20.21:49:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
In-reply-to
Content
Currently the documentation does sometimes say about specific exceptions but most times not. As I'm often catching exceptions to ensure a high stability this gets a little difficult. For example print() can trigger a BrokenPipeError and the most file functions like flush() can trigger other related IOError's.

So I would like to see something like a listing on every function which contains all exceptions that may appear. Also there are some special cases like close(). For example it can trigger an IOError too if there are pending write operations due to an implicit call of flush(). But if the file object is opened in read-only mode or there are no write operations this can't happen. Maybe such additional information can be added too.
History
Date User Action Args
2013-11-20 21:49:29Sworddragonsetrecipients: + Sworddragon, docs@python
2013-11-20 21:49:29Sworddragonsetmessageid: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
2013-11-20 21:49:29Sworddragonlinkissue19672 messages
2013-11-20 21:49:29Sworddragoncreate