On Fri, May 26, 2006 at 09:51:55PM -0700, Neal Norwitz wrote:
>I just hope to hell you're done, because I can't keep up! :-)
Yeah, sucks to be you. :-)
>It would help me enormously if someone could summarize the status and
>everything that went on. These are the things that would help me the
>m
"Steve Holden" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> It looks like there were a lot of additions to the string test suite,
>> that's great. I'm not sure if the other areas touched got similar
>> boosts to their tests. It would be good to upgrade all tests to
>> verify c
Neal Norwitz wrote:
> First off, good work to everyone involved. You did a tremendous job.
> I just hope to hell you're done, because I can't keep up! :-)
>
Not quite done yet, but I will be encouraging the team to start wrapping
up in time to draw a line under everything that *isn't* going to
> http://wiki.python.org/moin/NeedForSpeed/Successes
> http://wiki.python.org/moin/NeedForSpeed/Failures
> http://wiki.python.org/moin/NeedForSpeed/Deferred
And
http://wiki.python.org/moin/ListOfPerformanceRelatedPatches
All of these are linked to from the top page:
http://wiki.python.o
> It would help me enormously if someone could summarize the status and
> everything that went on. These are the things that would help me the
> most.
>
> * What are the speed diffs before/after the sprint
> * What was modified (summary)
> * What is left to do
>- doc
>- tests
>- code
First off, good work to everyone involved. You did a tremendous job.
I just hope to hell you're done, because I can't keep up! :-)
It would help me enormously if someone could summarize the status and
everything that went on. These are the things that would help me the
most.
* What are the spe
