I have seen a couple of objections to leaving unbound methods naked (as
functions) when retrieved in 3.0. Here is a plus.
A c.l.p poster reported that 2.6 broke his code because the addition of
default rich comparisons to object turned tests like hassattr(ob,
'__lt__') from False to True. Th
On Thu, Sep 4, 2008 at 12:36 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 3, 2008 at 9:25 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>> [Brett]
>>> I gave a talk last night at the Vancouver Python users group on
>>> 2.6/3.0, and I tried the following code and it failed during
Someone please fix the PEP. There are very good reasons for *not*
allowing "except X, Y:" to have a meaning -- if 2.x code somehow
accidentally ended up in the 3.0 world without having been run through
2to3, it would silently perturb the meaning in the most confusing way.
That's why the implementat
