title: "outsourcing" exception-handling to a decorator
body: <p>Many try/except/finally-clauses not only "uglify" my code, but i find myself often using identical exception-handling for similar tasks. So i was considering reducing redundancy by "outsourcing" them to a ... decorator.</p>
  
  <p>Because i was sure not to be the 1st one to come to this conclusion, I googled and found this - imho - ingenious <a href="http://code.activestate.com/recipes/408937-basic-exception-handling-idiom-using-decorators/" rel="noreferrer">recipe</a> which added the possibility to handle more than one exception.</p>
  
  <p>But i was surprised why this doesn't seem to be a wide known and used practice per se, so i was wondering if there is maybe an aspect i wasn't considering? </p>
  
  <ol>
  <li><p>Is it bogus to use the decorator pattern for exception-handling or did i just miss it the whole time? Please enlighten me! What are the pitfalls? </p></li>
  <li><p>Is there maybe even a package/module out there which supports the creation of such exception-handling in a reasonable way?</p></li>
  </ol>