Re: psycopg2: proper positioning of .commit() within try: except: blocks

Liste des GroupesRevenir à cl python 
Sujet : Re: psycopg2: proper positioning of .commit() within try: except: blocks
De : Karsten.Hilbert (at) *nospam* gmx.net (Karsten Hilbert)
Groupes : comp.lang.python
Date : 09. Sep 2024, 10:56:47
Autres entêtes
Message-ID : <mailman.1.1725872210.31645.python-list@python.org>
References : 1 2 3 4 5 6 7 8 9 10 11
Am Mon, Sep 09, 2024 at 01:48:32PM +1200 schrieb Greg Ewing via Python-list:

That code doesn't inspire much confidence in me. It's far too
convoluted with too much micro-management of exceptions.

It is catching two exceptions, re-raising both of them,
except for re-raising one of them as another kind of
exception.  What would you doing differently and how ?

I would much prefer to have just *one* place where exceptions are
caught and logged.

There's, of course, a top level handler which logs and
user-displays-as-appropriate any exceptions. This is code
from a much larger codebase.

Karsten
--
GPG  40BE 5B0E C98E 1713 AFA6  5BC0 3BEA AC80 7D4F C89B

Date Sujet#  Auteur
8 Sep 24 * Re: psycopg2: proper positioning of .commit() within try: except: blocks5Karsten Hilbert
9 Sep 24 `* Re: psycopg2: proper positioning of .commit() within try: except: blocks4Greg Ewing
9 Sep 24  +- Re: psycopg2 positioning of .commit() (Posting On Python-List Prohibited)1Lawrence D'Oliveiro
9 Sep 24  +- Re: psycopg2: proper positioning of .commit() within try: except: blocks1Karsten Hilbert
9 Sep 24  `- Re: psycopg2: proper positioning of .commit() within try: except: blocks1Karsten Hilbert

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal