Dennis Lee Bieber wrote:
> On Fri, 19 May 2006 14:41:13 +, [EMAIL PROTECTED] (Cameron Laird)
> declaimed the following in comp.lang.python: .
> > Guys, I try--I try *hard*--to accept the BetterToAskForgiveness
> > gospel, but this situation illustrates the discomfort I consistently
> >
Fredrik Lundh wrote:
> Cameron Laird wrote:
>
> > Guys, I try--I try *hard*--to accept the BetterToAskForgiveness
> > gospel, but this situation illustrates the discomfort I consistently
> > feel: how do I know that the NameError means VARIABLE didn't resolve,
> > rather than that it did, but that
"Fredrik Lundh" <[EMAIL PROTECTED]> writes:
> Cameron Laird wrote:
> > how do I know that the NameError means VARIABLE didn't resolve,
> > rather than that it did, but that evaluation of
> > commands.VARIABLE() itself didn't throw a NameError? My usual
> > answer: umm, unless I go to efforts to p
Fredrik Lundh wrote:
> Cameron Laird wrote:
>
>
>>Guys, I try--I try *hard*--to accept the BetterToAskForgiveness
>>gospel, but this situation illustrates the discomfort I consistently
>>feel: how do I know that the NameError means VARIABLE didn't resolve,
>>rather than that it did, but that eva
[Cameron]
> try:
> getattr(commands, VARIABLE)()
> except NameError:
> print >> sys.stderr, "Unknown command", VARIABLE
>
> this situation illustrates the discomfort I consistently
> feel: how do I know that the NameError means VARIABLE didn't resolve,
> rather than that it did, but that
Cameron Laird wrote:
> Guys, I try--I try *hard*--to accept the BetterToAskForgiveness
> gospel, but this situation illustrates the discomfort I consistently
> feel: how do I know that the NameError means VARIABLE didn't resolve,
> rather than that it did, but that evaluation of commands.VARIABLE
