New submission from Sworddragon:
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
R. David Murray added the comment:
This is not something we are going to do. We don't know what every exception
is that every function can raise.
Adding mentions of unusual special cases that aren't currently documented would
be OK, though. You should open specific issues for things you
Sworddragon added the comment:
I'm fine with this decision as it will be really much work. But this also means
programming with Python isn't considered for high stability applications - due
to the lack of important informations in the documentation.
An alternate way would be to rely on error
R. David Murray added the comment:
If switching to error codes would solve your problem, then catching Exception
at appropriate places should also solve your problem.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19672
Sworddragon added the comment:
Correct, but the second part of my last message was just my opinion that I
would prefer error codes over exceptions because it implies already a completed
documentation for this part due to return codes/error arguments/other potential
ways.
--
