Thanks, raise should do it. I read later on last night that raise called with nothing else re-raises the last exception, but never thought of using it in my situation.
On 10/20/11, Christian Witts <cwi...@compuscan.co.za> wrote: > On 2011/10/19 09:19 PM, Alex Hall wrote: >> Hi all, >> I have never done logging before, and I am wondering how it will >> change my script. Currently, I have something like this: >> for book in results: >> try: checkForErrors(book) >> except Exception, e: >> print e >> continue >> >> That way I see any errors in a given book, but that book is skipped >> and the loop continues. Now, though, checkForErrors() logs exceptions >> instead of raising them, so my try/except won't work, right? There is >> my question: if a method logs an exception instead of raising it, is >> that exception still raised by the logging module? Do I have to make >> checkForErrors() return something, and check for that, instead of >> using try/except or can I keep my loop how it is? TIA! >> > > If you have some exception handling and want it to propagate further up > the chain you can just raise it, for eg. > > def checkForErrors(book): > try: > do_something_that_could_raise_exceptions() > except Exception, e: > log_errors(e) > raise > > for book in results: > try: > checkForErrors(book) > except Exception, e: > do_your_other_exception_handling() > > -- > > Christian Witts > Python Developer > > // > -- Have a great day, Alex (msg sent from GMail website) mehg...@gmail.com; http://www.facebook.com/mehgcap _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
