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

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

Re: The Most Diabolical Python Antipattern

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: The Most Diabolical Python Antipattern Ethan Furman <ethan@stoneleaf.us> - 2015-01-29 09:49 -0800

#84832 — Re: The Most Diabolical Python Antipattern

[Multipart message — attachments visible in raw view] — view raw

On 01/29/2015 09:36 AM, Skip Montanaro wrote:
> On Thu, Jan 29, 2015 at 11:17 AM, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote:
>>
>> ... but what do you guys and gals think?
> 
> I saw that blog referenced elsewhere a day or two ago. I think he's
> correct. There are the occasional instance where I need to recover
> from an exception no matter what caused it. In cases where I fail to
> report the traceback somewhere, I'm often left scratching my head.

I agree -- worst practice.


> In my mind, this is approximately as bad as an external library
> (silently) calling exit().

Yeah, I hate when that happens.  I hate it even more when it's my own library. :/  (yeah, I fixed that!)

--
~Ethan~

[toc] | [standalone]

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

csiph-web