Oren <oren.leaf...@gmail.com> added the comment:
I totally agree that this involves misusing handleError. I ended up fixing the code that originally caused the problem, since it was wrong in the first place. The reason I filed this bug and that I think it's worth fixing is that in previous versions, the problem would be that something might not get logged as expected; now the problem turns into a crash. Not only is it now a crash, but the code that crashes requires something else to go wrong (we're not calling handleError() because everything went right), which means that applications that previously tolerated something going wrong, now break. If the necessary fix was complicated, I could see the wisdom in not fixing it, but since it's simple, why not? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34086> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
