Barry writes:
As an experiment, I just added a PEP topic to the python-checkins
mailing list. You could subscribe to this list and just select the PEP
topic (which matches the regex PEP in the Subject header or first few
lines of the body).
Give it a shot and let's see if that does the
I had been promising to rewrite PEP 246 to incorporate the last several
years' worth of discussions c about it, and Guido's recent stop the
flames artima blog post finally pushed me to complete the work.
Feedback is of course welcome, so I thought I had better repost it
here, rather than
On Mon, 2005-01-10 at 09:40, Michael Chermside wrote:
Barry writes:
As an experiment, I just added a PEP topic to the python-checkins
mailing list. You could subscribe to this list and just select the PEP
topic (which matches the regex PEP in the Subject header or first few
lines of the
I had been promising to rewrite PEP 246 to incorporate the last several
years' worth of discussions c about it, and Guido's recent stop the
flames artima blog post finally pushed me to complete the work.
Feedback is of course welcome, so I thought I had better repost it
here, rather than
On 2005 Jan 10, at 18:43, Phillip J. Eby wrote:
...
At 03:42 PM 1/10/05 +0100, Alex Martelli wrote:
The fourth case above is subtle. A break of substitutability can
occur when a subclass changes a method's signature, or restricts
the domains accepted for a method's argument
Alex Martelli [EMAIL PROTECTED] writes:
I didn't know about the let the object lie quirk in isinstance. If
that quirk is indeed an intended design feature, rather than an
implementation 'oops', it might perhaps be worth documenting it more
clearly; I do not find that clearly spelled out in
On Mon, Jan 10, 2005 at 01:34:59PM -0500, Phillip J. Eby wrote:
| The performance penalty I was talking about was for using an abstract
| base class, in a subclass with a __conform__ method for conformance to
| other protocols. In this case, __conform__ will be uselessly called
| every time
On Monday 10 January 2005 09:58 am, [EMAIL PROTECTED] wrote:
Message: 3
Date: Mon, 10 Jan 2005 07:46:39 -0800
From: Guido van Rossum [EMAIL PROTECTED]
Subject: Re: [Python-Dev] PEP 246, redux
To: Alex Martelli [EMAIL PROTECTED]
Cc: Clark C.Evans [EMAIL PROTECTED], Python Dev
On Mon, 10 Jan 2005 10:37:17 +1100, Andrew McNamara
[EMAIL PROTECTED] wrote:
csv.join(aList, e[, dialect='excel'[, fmtparam]]) - str object
Oops, should have been
csv.join(aList [, dialect='excel'[, fmtparam]]) - str object
Yes, it's feasible,
Good!
although newlines can be embedded in
At 04:16 PM 1/10/05 -0800, Michel Pelletier wrote:
From: Guido van Rossum [EMAIL PROTECTED]
Subject: Re: [Python-Dev] PEP 246, redux
I'm wondering if someone could do a similar thing for PEP 245,
interfaces syntax? Alex hinted that it's a couple of rounds behind the
developments in Zope and
Alex Martelli [EMAIL PROTECTED] writes:
PEP: 246
Title: Object Adaptation
Minor nit (or not?): You could provide a pointer to the Liskov
substitution principle, for those reader that aren't too familiar with
that term.
Besides, the text mentions three times that LiskovViolation is a
subclass
On Jan 10, 2005, at 16:38, Phillip J. Eby wrote:
At 07:42 PM 1/10/05 +0100, Alex Martelli wrote:
On 2005 Jan 10, at 18:43, Phillip J. Eby wrote:
...
I am not saying we shouldn't have a tp_conform; just suggesting that
it may be appropriate for functions and modules (as well as classic
At 05:42 PM 1/10/05 -0500, Bob Ippolito wrote:
On Jan 10, 2005, at 16:38, Phillip J. Eby wrote:
At 07:42 PM 1/10/05 +0100, Alex Martelli wrote:
On 2005 Jan 10, at 18:43, Phillip J. Eby wrote:
...
I am not saying we shouldn't have a tp_conform; just suggesting that it
may be appropriate for
Hi,
I've done a small patch to use linux AF_NETLINK sockets (see below).
Please comment!
Is there a reason for recvmsg() and sendmsg() not to be implemented
yet in socketmodule ?
The integration with autoconf has not been done, even if
this patch should be ok :
--- configure.in.ori
14 matches
Mail list logo
