Re: [Python-Dev] 2.5 status

On 9/7/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> > [MAL]> > The proper fix would be to introduce a tp_unicode slot and let> > this decide what to do, ie. call .__unicode__() methods on instances > > and use the .__name__ on classes.>> That was

Re: [Python-Dev] 2.5 status

On 9/7/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote:>> > [MAL]> > The proper fix would be to introduce a tp_unicode slot and let> > this decide what to do, ie. call .__unicode__() methods on instances > > and use the .__name__ on classes.>> That was

Re: [Python-Dev] 2.5 status

Doc patches are fine, please fix. n -- On 9/7/06, Ronald Oussoren <[EMAIL PROTECTED]> wrote: > > On 5-sep-2006, at 6:24, Neal Norwitz wrote: > > > There are 3 bugs currently listed in PEP 356 as blocking: > > http://python.org/sf/1551432 - __unicode__ breaks on > > exception classes > >

Re: [Python-Dev] 2.5 status

On 5-sep-2006, at 6:24, Neal Norwitz wrote: > There are 3 bugs currently listed in PEP 356 as blocking: > http://python.org/sf/1551432 - __unicode__ breaks on > exception classes > http://python.org/sf/1550938 - improper exception w/ > relative import > http://python.or

Re: [Python-Dev] 2.5 status

On 9/5/06, Brett Cannon <[EMAIL PROTECTED]> wrote: > > > [MAL] > > The proper fix would be to introduce a tp_unicode slot and let > > this decide what to do, ie. call .__unicode__() methods on instances > > and use the .__name__ on classes. > > That was my bug reaction and what I said on the bug r

Re: [Python-Dev] 2.5 status

On 9/5/06, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: Brett Cannon wrote:> On 9/4/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: There are 3 bugs currently listed in PEP 356 as blocking:>> http://python.org/sf/1551432 - __unicode__ breaks on exception>> classes>>> I replied on the bug repor

Re: [Python-Dev] 2.5 status

Brett Cannon wrote: > On 9/4/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: >> >> There are 3 bugs currently listed in PEP 356 as blocking: >> http://python.org/sf/1551432 - __unicode__ breaks on exception >> classes > > > I replied on the bug report, but might as well comment here. > > The

Re: [Python-Dev] 2.5 status

On 9/5/06, Georg Brandl <[EMAIL PROTECTED]> wrote: Brett Cannon wrote:>>> On 9/4/06, *Neal Norwitz* <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote: >> There are 3 bugs currently listed in PEP 356 as blocking:> http://python.org/sf/1551432 - __unicode__ breaks on> exception classe

Re: [Python-Dev] 2.5 status

Brett Cannon wrote: > > > On 9/4/06, *Neal Norwitz* <[EMAIL PROTECTED] > > wrote: > > There are 3 bugs currently listed in PEP 356 as blocking: > http://python.org/sf/1551432 - __unicode__ breaks on > exception classes > > > I replied on the bug re

Re: [Python-Dev] 2.5 status

On 9/4/06, Neal Norwitz <[EMAIL PROTECTED]> wrote: There are 3 bugs currently listed in PEP 356 as blocking:http://python.org/sf/1551432 - __unicode__ breaks on exception classesI replied on the bug report, but might as well comment here. The problem with this bug is that BaseException now

[Python-Dev] 2.5 status

There are 3 bugs currently listed in PEP 356 as blocking: http://python.org/sf/1551432 - __unicode__ breaks on exception classes http://python.org/sf/1550938 - improper exception w/relative import http://python.org/sf/1541697 - sgmllib regexp bug causes hang Does anyone wan

Re: [Python-Dev] 2.5 status

Tim Peters wrote: > [Georg Brandl, on > http://python.org/sf/1523610 - PyArg_ParseTupleAndKeywords > potential core dump > ] >> This one's almost fixed if we can decide what to do with "levels". >> I wrote some time ago: >> >> """ >> With respect to this bug (which is about stack issues in Pyt

Re: [Python-Dev] 2.5 status

[Georg Brandl, on http://python.org/sf/1523610 - PyArg_ParseTupleAndKeywords potential core dump ] > This one's almost fixed if we can decide what to do with "levels". > I wrote some time ago: > > """ > With respect to this bug (which is about stack issues in Python/getargs.c > involving misus

Re: [Python-Dev] 2.5 status

Martin v. Löwis wrote: > [EMAIL PROTECTED] schrieb: >> >>> class X(object): >> ... def __hash__(self): return id(self) >> ... >> >>> hash (X()) >> Traceback (most recent call last): >> File "", line 1, in >> OverflowError: long int too la

Re: [Python-Dev] 2.5 status

[EMAIL PROTECTED] schrieb: > The code (exception handler added to demonstrate and work around > the problem): > > try : > h = hash(p) > except OverflowError, e: > print type(p), p, id(p), e > h = id

Re: [Python-Dev] 2.5 status

"Neal Norwitz" <[EMAIL PROTECTED]> wrote: > Things are getting better, but we still have some really important > outstanding issues. PLEASE CONTINUE TESTING AS MUCH AS POSSIBLE. I've run into a problem with a big application that I wasn't able to reproduce with a small example. I've submitted a

Re: [Python-Dev] 2.5 status

Neal Norwitz wrote: > Things are getting better, but we still have some really important > outstanding issues. PLEASE CONTINUE TESTING AS MUCH AS POSSIBLE. > Also, it would be great to use as many tools as possible to find bugs > and improve quality. It would be especially nice to run Purify on >

Re: [Python-Dev] 2.5 status

Neal Norwitz wrote: > I believe all 3 outstanding issues (and solutions!) could use some > more discussion. All bugs/patches blocking release are set to > priority 9. > > http://python.org/sf/1530559 - struct rejecting floats (patch pending) > > http://mail.python.org/pipermail/p

[Python-Dev] 2.5 status

Things are getting better, but we still have some really important outstanding issues. PLEASE CONTINUE TESTING AS MUCH AS POSSIBLE. Also, it would be great to use as many tools as possible to find bugs and improve quality. It would be especially nice to run Purify on Windows. I've updated PEP 35