-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
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
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
>>
-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 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
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 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
-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 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 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:
> -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
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."
___
-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
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
I just committed r64651 which is my attempt to add support to
fix_imports so that modules that have been split up in 3.0 can be
properly fixed. 2to3's test suite passes and all, but I am not sure if
I botched it somehow since I did the change slightly blind. Can
someone just do a quick check to mak
On Tue, Jul 1, 2008 at 9:04 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I just committed r64651 which is my attempt to add support to
> fix_imports so that modules that have been split up in 3.0 can be
> properly fixed. 2to3's test suite passes and all, but I am not sure if
> I botched it somehow
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
-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 7:38 PM, Benjamin Peterson
<[EMAIL PROTECTED]> wrote:
> On Tue, Jul 1, 2008 at 9:04 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>> I just committed r64651 which is my attempt to add support to
>> fix_imports so that modules that have been split up in 3.0 can be
>> properly fi
Hi,
I remember discussing this before and coming to conclusion that
-fno-strict-aliasing would be removed from py3k CFLAGS. But as of now
its still used.
I tested with gcc 4.3.1 on Linux x86_64 and there is no strict
aliasing warning when this flag is removed. Also make testall passes.
Is there a
Hi,
I'd like extra opinions on this issue please:
http://bugs.python.org/issue3214
It's about changing the definition of Duck typing to remove hasattr and
leave just EAFP in the enablers - more detail is in the issue log.
Thanks, Paddy.
___
Python-Dev
On Tue, Jul 1, 2008 at 8:36 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 1, 2008 at 7:38 PM, Benjamin Peterson
> <[EMAIL PROTECTED]> wrote:
>> On Tue, Jul 1, 2008 at 9:04 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>> I just committed r64651 which is my attempt to add support to
>>> f
22 matches
Mail list logo
