On 12/10/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
> Barry Warsaw <[EMAIL PROTECTED]> writes:
>
> > Let's say something like "string-based exceptions are strongly
> > discouraged, and in fact may be deprecated or disappear in a future
> > Python version. Use class-based exceptions."
>
> If I h
[Ian Bicking]
>Barry Warsaw wrote:
>Just like I wouldn't like someone using "self" outside of the first
>argument of instance methods.
A tiny nit. Within __new__(cls, ...), I find quite legible writing:
self = BASECLASSE.__new__(cls, ...)
and using it afterwards.
--
François Pinard ht
Nick Coghlan <[EMAIL PROTECTED]> writes:
> Michael Hudson wrote:
>> (PS: are people still interested in my new-style exceptions patch?
>> http://bugs.python.org/1104669)
>
> Is there a specific concern with it you want people to check out, or just a
> few more "works for me" tests on different p
Michael Hudson wrote:
> Barry Warsaw <[EMAIL PROTECTED]> writes:
>
>> Let's say something like "string-based exceptions are strongly
>> discouraged, and in fact may be deprecated or disappear in a future
>> Python version. Use class-based exceptions."
>
> If I have anything to do with it, they _
Barry Warsaw <[EMAIL PROTECTED]> writes:
> Let's say something like "string-based exceptions are strongly
> discouraged, and in fact may be deprecated or disappear in a future
> Python version. Use class-based exceptions."
If I have anything to do with it, they _will_ be deprecated in 2.5.
There
Robert Brewer wrote:
> Barry Warsaw wrote:
>
>>Again, I'd say something like: Since your exceptions
>>will be classes, use the CapWord naming convention for
>>classes to name your exceptions. It is recommended
>>that your exception class end in the word "Error".
>
>
> Unless, of course, your exc
