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


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

Re: Proposed new conditional operator: "or else"

Started byTim Chase <python.list@tim.thechases.com>
First post2014-12-03 05:59 -0600
Last post2014-12-03 05:59 -0600
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: Proposed new conditional operator: "or else" Tim Chase <python.list@tim.thechases.com> - 2014-12-03 05:59 -0600

#81857 — Re: Proposed new conditional operator: "or else"

FromTim Chase <python.list@tim.thechases.com>
Date2014-12-03 05:59 -0600
SubjectRe: Proposed new conditional operator: "or else"
Message-ID<mailman.16532.1417608313.18130.python-list@python.org>
On 2014-12-02 23:05, Dennis Lee Bieber wrote:
> >   foo == 42 or else
> 
> 	Has a PERL stink to it... like: foo == 42 or die

This statement actually works in Python and I occasionally use it
when debugging (in the same fashion as one might do printf()
debugging in C).  It raises a NameError and the program dies with a
traceback.  Most frequently, it's to prevent the program from
continuing on to connect to a database and actually make changes.

I've grown up a bit and usually use pdb.set_trace() now, but it's
still in my grab-bag of tools.

-tkc


[sorry for the previous message if I failed to cancel the send that
happened when I accidentally pressed ctrl+enter...typing in the dark]


[toc] | [standalone]


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


csiph-web