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


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

Re: Interface and duck typing woes

Started byChris Angelico <rosuav@gmail.com>
First post2013-08-29 09:17 +1000
Last post2013-08-29 09:17 +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: Interface and duck typing woes Chris Angelico <rosuav@gmail.com> - 2013-08-29 09:17 +1000

#53193 — Re: Interface and duck typing woes

FromChris Angelico <rosuav@gmail.com>
Date2013-08-29 09:17 +1000
SubjectRe: Interface and duck typing woes
Message-ID<mailman.331.1377731849.19984.python-list@python.org>
On Thu, Aug 29, 2013 at 7:54 AM, Terry Reedy <tjreedy@udel.edu> wrote:
> Depending on who the users will be, I might just not worry about it until an
> exception is raised. If you try to protect against everything that you might
> do wrong, you are on the road to madness, as the protection code might also
> be buggy. (Too much testing has the same problem ;-).

I'd go further.

Do you believe that you can write code to catch every bug you might
make? If so, you are naive and probably haven't spent much time
programming yet :) And if not, then you must acknowledge that bugs
WILL happen; therefore you will need to cope with them after the
event. So rather than trying to prevent them all, just improve your
means of coping, and you'll accomplish the same end with much less
trouble.

At this point I could go off into a lengthy discussion of philosophy
and original sin (not "original SYN", which is a different thing
altogether), but anyone who's ever written bug-handling code will
understand what I mean already :)

ChrisA

[toc] | [standalone]


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


csiph-web