-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 10:42 PM, Benjamin Peterson wrote:
On Tue, Jul 1, 2008 at 8:44 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
Is a Google Calendar kep
On Tue, Jul 1, 2008 at 8:44 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
>>
>> Is a Google Calendar kept by anyone that lists stuff like planned
>> release dates, etc.?
>
> http://www.google.com/cal
On Tue, Jul 1, 2008 at 6:44 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
>
>> On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:27 PM, Brett Cannon wrote:
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 1:51
Hi,
the download page (http://www.python.org/download/releases/3.0/) for
Python 3000 shows :
9119625244b17aa35ed94b655a2b2135 13491200 python-3.0b1.msi
but I got
9119625244a57aa35ed94b655a2b2135 13491200 python-3.0b1.msi
(44a57 rather than 44b17 )
with several md5 checkers (
On Tue, Jul 1, 2008 at 6:27 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> Is a Google Calendar kept by anyone that lists stuff like planned
> release dates, etc.?
It's on my personal one. :)
--
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."
___
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
>
>> On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>> From: "Barry Warsaw" <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 7:04 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]>
On Tue, Jul 1, 2008 at 3:55 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
>> On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
>> From: "Barry Warsaw" <[EMAIL PROTECTED]>
>>
>> There are two options. I could shift every
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 1, 2008, at 4:54 PM, Guido van Rossum wrote:
On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]>
wrote:
From: "Barry Warsaw" <[EMAIL PROTECTED]>
There are two options. I could shift everything forward 2 weeks
and do t
On Tue, Jul 1, 2008 at 1:51 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> From: "Barry Warsaw" <[EMAIL PROTECTED]>
>
>> 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 bet
From: "Barry Warsaw" <[EMAIL PROTECTED]>
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.
+1 for six weeks to allow the code to be mo
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
On Tue, Jul 1, 2008 at 5:37 AM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> http://bugs.python.org/issue3247 complains that with python 3.0, dir()
> of a SRE_Match object returns an empty list.
>
> This type has the particularity to not define a tp_methods; instead,
> its tp_getattr slot call
Hello,
http://bugs.python.org/issue3247 complains that with python 3.0, dir()
of a SRE_Match object returns an empty list.
This type has the particularity to not define a tp_methods; instead,
its tp_getattr slot calls Py_FindMethod(match_methods, self, name)
where "match_methods" is a PyMethodDef
22 matches
Mail list logo
