Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #109174 > unrolled thread

Re: Handling exceptions with Py2 and Py3

Started byBen Finney <ben+python@benfinney.id.au>
First post2016-05-28 00:04 +1000
Last post2016-05-28 00:04 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Handling exceptions with Py2 and Py3 Ben Finney <ben+python@benfinney.id.au> - 2016-05-28 00:04 +1000

#109174 — Re: Handling exceptions with Py2 and Py3

FromBen Finney <ben+python@benfinney.id.au>
Date2016-05-28 00:04 +1000
SubjectRe: Handling exceptions with Py2 and Py3
Message-ID<mailman.23.1464357859.2277.python-list@python.org>
Random832 <random832@fastmail.com> writes:

> On Fri, May 27, 2016, at 09:18, Ben Finney wrote:
> >     try:
> >         short_routine()
> >     except ConnectionRefusedError as exc:
> >         handle_connection_refused(exc)
> >     except OSError as exc:
> >         if exc.errno == errno.ECONNREFUSED:
> >             handle_connection_refused(exc)
>
> But ConnectionRefusedError inherits from OSError and has errno =
> ECONNREFUSED. So you can simply only have the second except block here,
> and ignore the fact that Python 3 has a class hierarchy of error types.

That's right. I wrote the above to isolate the older clumsy way, and
make it easier to remove.

Every Python 2-and-3 code base should aspire to one day discard the
Python 2 legacy cruft :-)

-- 
 \         “For a sentimentalist is simply one who desires to have the |
  `\    luxury of an emotion without paying for it.” —Oscar Wilde, _De |
_o__)                                                 Profundis_, 1897 |
Ben Finney

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web