Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #46208
| From | Carlos Nepomuceno <carlosnepomuceno@outlook.com> |
|---|---|
| Subject | RE: Python error codes and messages location |
| Date | 2013-05-27 19:54 +0300 |
| References | <CAA=1kxR=05RbcbR8s1rzfdQBGXGRRx2j=O8NpcEFB-_GiZBJPg@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2255.1369673709.3114.python-list@python.org> (permalink) |
Thanks so much guys! I'm not planning to prepare for every possible situation, but I certainly am responsible to handle most common errors. So it's really important to know what a function/method returns when called. Exception handling may take lots of code, but I'm used to it. It's much better to have a graceful shutdown than a data/time loss. ;) I think PEP 3151 is a step ahead! That's almost exactly what I was looking for. Why did it take so long to have that implemented?
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Python error codes and messages location Fábio Santos <fabiosantosart@gmail.com> - 2013-05-27 13:46 +0100
Re: Python error codes and messages location Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-05-27 13:11 +0000
Re: Python error codes and messages location Fábio Santos <fabiosantosart@gmail.com> - 2013-05-27 14:26 +0100
RE: Python error codes and messages location Carlos Nepomuceno <carlosnepomuceno@outlook.com> - 2013-05-27 19:54 +0300
Re: Python error codes and messages location Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-05-27 18:14 +0100
Re: Python error codes and messages location Terry Jan Reedy <tjreedy@udel.edu> - 2013-05-27 13:52 -0400
csiph-web