In article ,
Gary Herron wrote:
> On 10/02/2011 05:24 PM, Kevin Walzer wrote:
> > Turns out the error was a typo in the actual method being
> > called...*faceinhands*
> >
> > Sorry for the noise.
> >
>
> But this is a great example of why you should not use a naked except
> clause. As state
On 10/02/2011 05:24 PM, Kevin Walzer wrote:
Turns out the error was a typo in the actual method being
called...*faceinhands*
Sorry for the noise.
But this is a great example of why you should not use a naked except
clause. As stated, your code will execute the except clause for *any*
kin
Turns out the error was a typo in the actual method being
called...*faceinhands*
Sorry for the noise.
--
Kevin Walzer
Code by Kevin
http://www.codebykevin.com
--
http://mail.python.org/mailman/listinfo/python-list
On Sun, 02 Oct 2011 18:02:05 -0400, Kevin Walzer wrote:
> I'm seeing a very odd error in an application I'm developing using
> Python 2.7.2, on Mac OS 10.7.
>
> This application uses a wrapper method to look up other method names via
> getattr and then call those methods. I have not previously ha
On 10/2/2011 6:02 PM, Kevin Walzer wrote:
I'm seeing a very odd error in an application I'm developing using
Python 2.7.2, on Mac OS 10.7.
This application uses a wrapper method to look up other method names via
getattr and then call those methods. I have not previously had an issue
with this na
On Sun, Oct 2, 2011 at 3:02 PM, Kevin Walzer wrote:
> I'm seeing a very odd error in an application I'm developing using Python
> 2.7.2, on Mac OS 10.7.
>
> This application uses a wrapper method to look up other method names via
> getattr and then call those methods. I have not previously had an
I'm seeing a very odd error in an application I'm developing using
Python 2.7.2, on Mac OS 10.7.
This application uses a wrapper method to look up other method names via
getattr and then call those methods. I have not previously had an issue
with this name, but for some reason this functionali
