> "BAW" == Barry Warsaw <[EMAIL PROTECTED]> writes:
BAW> So are you saying that moving to svn will let us do more long
BAW> lived branches? Yay!
Yes, but you still have to be disciplined about it. svn is not much
better than cvs about detecting and ignoring spurious conflicts due to
Nick Coghlan wrote:
> New Hierarchy
> =
>
> Raisable (formerly Exception)
> +-- CriticalException (new)
> +-- KeyboardInterrupt
> +-- MemoryError
> +-- SystemError
> +-- ControlFlowException (new)
> +-- GeneratorExit
> +-- StopIteration
> +-- SystemExit
>
Hi,
I'm attempting to write a Packet class, and a few other classes for
use in writing protocol conformance tests. For the most part this is
going well except that I'd like to be able to pack and unpack byte
strings with values that are not 8 bit based quantities. As an
example, I'd like to be a
At 12:12 PM 7/31/2005 -0400, James Y Knight wrote:
>On Jul 30, 2005, at 8:57 PM, Nick Coghlan wrote:
> > I wouldn't mind using Exception/Error instead of Raisable/Exception
> > - and it
> > seriously reduces the pain of making this transition. Indeed, most
> > of it
> > becomes doable within the 2.
On Sunday 31 July 2005 12:17, Brett Cannon wrote:
> Yeah, those explanations work for me. I think I am going to have to
> write an explanation for every exception so its usage is clear.
That said, I agree with Phillip; a KeyboardInterrupt isn't an error, it's
asynchronous user input. That mak
On 7/31/05, Willem Broekema <[EMAIL PROTECTED]> wrote:
> On 7/31/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > While we do tend to use KeyboardInterrupt as a way to kill a
> > program, is that really control flow, or a critical exception
> > that the program needs to stop because an serious event
On 7/31/05, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> >>Notice that I've classified KeyboardInterrupt as user-initiated control flow
> >>and put it under ControlFlowException above. This means that everything
> >>under
> >>CriticalError and Error actually ends with the word '
At 05:05 PM 7/31/2005 +1000, Nick Coghlan wrote:
>Brett Cannon wrote:
> >>Notice that I've classified KeyboardInterrupt as user-initiated control
> flow
> >>and put it under ControlFlowException above. This means that everything
> under
> >>CriticalError and Error actually ends with the word 'Err
On 7/30/05, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
> On Saturday 30 July 2005 22:20, Brett Cannon wrote:
> > True, but the hierarchy should still properly reflect increasing
> > severity in my opinion. I am going to push for this; we will see if I
> > get pushed back enough to not do it.
On Jul 30, 2005, at 8:57 PM, Nick Coghlan wrote:
> I wouldn't mind using Exception/Error instead of Raisable/Exception
> - and it
> seriously reduces the pain of making this transition. Indeed, most
> of it
> becomes doable within the 2.x series - the only tricky parts are
> semantic
> change
On Sunday 31 July 2005 06:36, Willem Broekema wrote:
> I does not seem right to me to think of KeyboardInterrupt as a means
> to cause program halting. An interpreter could in principle recover
> from it and resume execution of the program.
Somewhat. An interrupt may well not mean that the pro
Willem Broekema wrote:
> On 7/31/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
>
>>While we do tend to use KeyboardInterrupt as a way to kill a
>>program, is that really control flow, or a critical exception
>>that the program needs to stop because an serious event
>>occurred?
>
>
> I does not see
On 7/31/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> While we do tend to use KeyboardInterrupt as a way to kill a
> program, is that really control flow, or a critical exception
> that the program needs to stop because an serious event
> occurred?
I does not seem right to me to think of KeyboardI
Brett Cannon wrote:
>>Notice that I've classified KeyboardInterrupt as user-initiated control flow
>>and put it under ControlFlowException above. This means that everything under
>>CriticalError and Error actually ends with the word 'Error'.
>
> I don't know if I like this change in inheritance.
14 matches
Mail list logo
