At 12:25 PM 8/2/2005 +0900, Stephen J. Turnbull wrote:
> > "Willem" == Willem Broekema <[EMAIL PROTECTED]> writes:
>
> Willem> So, in short, Keyboard interrupts in Lisp are a
> Willem> serious-condition, not an error.
>
> Willem> (And what is labeled CriticalException in this discus
At Mon, 01 Aug 2005 10:52:03 -0700,
Donovan Baarda wrote:
>
> On Sun, 2005-07-31 at 23:54, Stephen J. Turnbull wrote:
> > > "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!
> >
> "Willem" == Willem Broekema <[EMAIL PROTECTED]> writes:
Willem> So, in short, Keyboard interrupts in Lisp are a
Willem> serious-condition, not an error.
Willem> (And what is labeled CriticalException in this discussion,
Willem> has in serious-condition Lisp's counterpart.)
Brett Cannon wrote:
> The problem with subclassing NotImplementedError is you need to
> remember it is used to signal that a magic method does not work for a
> specific type and thus should try the __r*__ version.
No, that's done by *returning* NotImplemented, not by
raising an exception at all.
> "Donovan" == Donovan Baarda <[EMAIL PROTECTED]> writes:
Donovan> Yeah. IMHO the sadest thing about SVN is it doesn't do
Donovan> branch/merge properly. All the other cool stuff like
Donovan> renames etc is kinda undone by that. [...] This is why
Donovan> I don't bother migr
On Thursday 28 July 2005 13:00, Martin v. Löwis wrote:
> I'd like to see the Python source be stored in Subversion instead
> of CVS,
I'm +1 on this, assuming we use the fsfs backend, and not the berkeley
DB one. I'm -1 if we're using the bdb backend (I've had nothing but
pain from it).
> CVS ha
On 8/1/05, Delaney, Timothy (Tim) <[EMAIL PROTECTED]> wrote:
> Nick Coghlan wrote:
>
> > +-- Exception (formerly StandardError)
> > +-- AttributeError
> > +-- NameError
> > +-- UnboundLocalError
> > +-- RuntimeError
> > +-- NotImplementedError
>
> Time to wade in
Nick Coghlan wrote:
> +-- Exception (formerly StandardError)
> +-- AttributeError
> +-- NameError
> +-- UnboundLocalError
> +-- RuntimeError
> +-- NotImplementedError
Time to wade in ...
I've actually been wondering if NotImplementedError should actually be a
sub
On 8/1/05, Stephen J. Turnbull <[EMAIL PROTECTED]> wrote:
> Uh, according to your example in Common LISP it is indeed an error,
I think you are referring to the first word of this line:
Error: Received signal number 2 (Keyboard interrupt) [condition type:
INTERRUPT-SIGNAL]
Well, that refers to
On Mon, 2005-08-01 at 10:36, Gabriel Becedillas wrote:
> Hi,
> We embbeded Python 2.0.1 in our product a few years ago and we'd like to
> upgrade to Python 2.4.1. This was not a simple task, because we needed
> to execute syscalls on a remote host. We modified Python's source code
> in severall p
On Sun, 2005-07-31 at 23:54, Stephen J. Turnbull wrote:
> > "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
>
Hi,
We embbeded Python 2.0.1 in our product a few years ago and we'd like to
upgrade to Python 2.4.1. This was not a simple task, because we needed
to execute syscalls on a remote host. We modified Python's source code
in severall places to call our own versions of some functions. For
example, i
> "Willem" == Willem Broekema <[EMAIL PROTECTED]> writes:
Willem> I hope the above makes the way I'm thinking more clear.
Willem> Like Phillip J. Eby, I think that labeling
Willem> KeyboardInterrupt a CriticalException seems wrong; it is
Willem> not an error and not critical.
Willem Broekema <[EMAIL PROTECTED]> writes:
> I realize it's major work to add recovery features to the CPython
> interpreter, so I don't think CPython will have anything like it soon
> and therefore also Python-the-language will not. Instead, my reason
> for mentioning this is to get the _concept
"George V. Neville-Neil" <[EMAIL PROTECTED]> writes:
> 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
On 7/31/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 7/31/05, Willem Broekema <[EMAIL PROTECTED]> 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 progr
16 matches
Mail list logo
