Bruno Lalande <bruno.lalande <at> gmail.com> writes:
Beside the fact that I completely agree with you (but probably because I'm a C++ developer), you have to be aware that Python and C++ philosophies differ dramatically. On this precise point, while C++ developers are attached to a well-defined balance between return codes and exceptions, Python has pushed the use of exceptions to an extreme. This often leads to things that are considered as worst practices and/or beginner mistakes in other languages, like the fact of stopping an iteration by throwing. In Python, the assertion that "exceptions should only handle errors" is unfortunately false.
I guess it's ok. To the point where Boost.Python starts to throw C++ exceptions. Why does library chosen to follow python practice and not C++ is unclear to me. Gennadiy