make IOError exceptions during POST data read() easy to identify
|Reported by:||J. David Lowe||Owned by:||nobody|
|Cc:||grahamd, Carl Meyer||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
In short, I want to be able to suppress the IOError exceptions that are raised under common, but completely uncontrollable, client conditions e.g. connection abruptly closed. Like others, though, I find it unacceptable to completely suppress IOError exceptions, though -- it's a very broad exception class, and I don't want to hide real bugs.
The attached patch addresses this by catching IOErrors that occur while read()ing POST data, and re-throwing them as a new subclass of IOError.
Cc: grahamd and carljm, who are associated with the other two tickets.
Change History (8)
comment:1 Changed 5 years ago by
|Patch needs improvement:||unset|
|Triage Stage:||Unreviewed → Design decision needed|
comment:3 Changed 5 years ago by
|Patch needs improvement:||set|
|Triage Stage:||Design decision needed → Accepted|