cascading python executions only if return code is 0

Chris Angelico rosuav at gmail.com
Fri Dec 27 03:27:41 CET 2013


On Fri, Dec 27, 2013 at 1:20 PM, Dennis Lee Bieber
<wlfraed at ix.netcom.com> wrote:
> On Fri, 27 Dec 2013 12:44:35 +1100, Chris Angelico <rosuav at gmail.com>
> declaimed the following:
>
>>On Fri, Dec 27, 2013 at 12:37 PM, Roy Smith <roy at panix.com> wrote:
>>> How about this one, that I wrote yesterday;
>>>
>>>         assert second >= self.current_second, "time went backwards"
>>>
>>> I think that's pretty high up on the "can never happen" list.
>>
>>assert second >= self.current_second, "user changed the clock"
>>
>         Why blame the user if an NTP synch made the adjustment? <G>

True, it could have been NTP, or maybe the original assert was right
and we're on the other side of an event horizon. But it's much more
fun to blame the user.

ChrisA



More information about the Python-list mailing list