-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:43 PM, Antoine Pitrou wrote:
By the way, Barry, did you read the thread about regexps behaviour
vis-à-vis
bytes and unicode? Your advice was requested :-)
See http://mail.python.org/pipermail/python-3000/2008-June/014247.html
On Tue, Jul 1, 2008 at 3:40 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>
> There are two options. I could shift everything forward 2 weeks and do the
> next betas on July 16th. Or we could wait until August 6th. That would
> mean 6 weeks between betas. It's fine with me either way.
I vote for
Hello,
> I know it's good to follow the release plan, but it
> also may save you, the release manager, work for the third beta (which
> I think will be necessary if beta2 is released tomorrow).
Yes, there are a lot of things remaining to do before Python 3.0 is sufficiently
polished. For example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:25 PM, Guido van Rossum wrote:
I think we should put this one off. The previous betas were done on
June 18, and IMO the next beta should be about a month afterwards,
not 2 weeks.
I will not be able to make releases the week
On Tue, Jul 1, 2008 at 4:23 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Barry Warsaw schrieb:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Wow, I bet this one crept up on you as quickly as it did me!
>>
>> We have our second planned beta releases for 2.6 and 3.0 tomorrow. As
>>
I think we should put this one off. The previous betas were done on June 18,
and IMO the next beta should be about a month afterwards, not 2 weeks.
On Tue, Jul 1, 2008 at 1:16 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wow, I bet this one cre
Barry Warsaw schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow, I bet this one crept up on you as quickly as it did me!
We have our second planned beta releases for 2.6 and 3.0 tomorrow. As
usual I will start looking at blockers and buildbots tomorrow
afternoon (UTC-4 time) with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow, I bet this one crept up on you as quickly as it did me!
We have our second planned beta releases for 2.6 and 3.0 tomorrow. As
usual I will start looking at blockers and buildbots tomorrow
afternoon (UTC-4 time) with a plan to start building
