Re: [Python-Dev] [Python-checkins] r46043 - peps/trunk/pep-0356.txt

2006-05-22 Thread skip
Tim If there's no functionality changes, what would be the problem with Tim putting it in post-alpha? It still represents new code that may introduce new bugs. In theory (and generally in practice for Python), once you move into the beta stage all you do is fix bugs. Skip

Re: [Python-Dev] [Python-checkins] r46043 - peps/trunk/pep-0356.txt

2006-05-22 Thread Thomas Wouters
On 5/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Tim If there's no functionality changes, what would be the problem withTim putting it in post-alpha?It still represents new code that may introduce new bugs.In theory (andgenerally in practice for Python), once you move into the beta stage all

Re: [Python-Dev] [Python-checkins] r46043 - peps/trunk/pep-0356.txt

2006-05-22 Thread Delaney, Timothy (Tim)
Thomas Wouters wrote: On 5/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Tim If there's no functionality changes, what would be the problem with Tim putting it in post-alpha? It still represents new code that may introduce new bugs. In theory (and generally in practice for

Re: [Python-Dev] [Python-checkins] r46043 - peps/trunk/pep-0356.txt

2006-05-19 Thread Steve Holden
neal.norwitz wrote: Please note that the Need for Speed sprint runs May 21 - 27. Bringing the schedule forward on Alpha 3 makes it less possible to incorporate sprint changes into the 2.5 trunk. Will it be acceptable to add new (performance) changes between Alpha 3 and beta 1, or would