On Thu, Jul 17, 2008 at 12:30 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We have green buildbots, yay! Thanks everyone for that.
>
> However, we still have three release blocker issues that I am not
> comfortable deferring.
>
> 3088 test_multi
Barry Warsaw wrote:
[...]
I'll note that I plan to hold the beta3 releases until all release
blocker and deferred blockers are resolved.
Ian Ozsvald of ShowMeDo.com noticed a blog post of mine about this beta,
and responded as follows:
Re.
http://holdenweb.blogspot.com/2008/07/cpython-ge
On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
> 3375: Guido (thanks guido) looked into this, and while I banged my
> head on it a lot yesterday - guido's identified the issue, and now I
> need to figure out a fix - help is welcome on this one.
You're welcome. I would hav
On Thu, Jul 17, 2008 at 10:07 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
>> 3375: Guido (thanks guido) looked into this, and while I banged my
>> head on it a lot yesterday - guido's identified the issue, and now I
>> n
On Wed, Jul 16, 2008 at 11:30 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We have green buildbots, yay! Thanks everyone for that.
The Windows buildbots are not very happy, though. test_ssl and
test_bsddb and constantly failing on both the trun
On Thu, Jul 17, 2008 at 8:36 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 10:07 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> On Thu, Jul 17, 2008 at 6:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
>>> 3375: Guido (thanks guido) looked into this, and while I banged my
> test_ssl ... constantly failing on both the trunk and py3k.
I'll take a closer look at this. It's the new test added in lately.
Seems to be working on non-Windows platforms, so I'm guessing it's
some Windows oddity, which I'm not very good at diagnosing. Worst
comes to worst, we can take out t
> > test_ssl ... constantly failing on both the trunk and py3k.
>
> I'll take a closer look at this. It's the new test added in lately.
> Seems to be working on non-Windows platforms, so I'm guessing it's
> some Windows oddity, which I'm not very good at diagnosing. Worst
> comes to worst, we ca
On Thu, Jul 17, 2008 at 9:16 AM, Jesse Noller <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 12:30 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> We have green buildbots, yay! Thanks everyone for that.
>>
>> However, we still have three
> The Windows buildbots are not very happy, though. test_ssl ...
> constantly failing on both the trunk and py3k.
I've checked in patches for test_ssl on both branches. Let's see how
the Windows buildbots do.
Bill
___
Python-3000 mailing list
Python-30
Hi,
it would be nice if someone could take a look at the patch for issue 2523. Right
now it takes py3k 30 seconds at 100% CPU to read a 10MB binary file.
Thanks
Antoine.
___
Python-3000 mailing list
[email protected]
http://mail.python.org/mail
http://bugs.python.org/issue3400
dis / Python Bytecode Instructions doc is missing entries for
UNPACK_EX
STORE_LOCALS
LOAD_BUILD_CLASS
MAKE_BYTES
which appear in dis.opname (3.0 version).
Based on examples, I suggested that the UNPACK_SEQUENCE entry be followed by
UNPACK_EX(bytepair)
Used for s
> The Windows buildbots are not very happy, though. test_ssl and
> test_bsddb and constantly failing on both the trunk and py3k. I don't
> know much about either of these items (or Windows for that matter), so
> any help would be greatly appreciated.
bsddb is in a very bad shape, as the 2.6 code h
On Thu, Jul 17, 2008 at 6:27 PM, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
>> The Windows buildbots are not very happy, though. test_ssl and
>> test_bsddb and constantly failing on both the trunk and py3k. I don't
>> know much about either of these items (or Windows for that matter), so
>> any h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 18, 2008, at 01:27 AM, Martin v. Löwis wrote:
>> The Windows buildbots are not very happy, though. test_ssl and
>> test_bsddb and constantly failing on both the trunk and py3k. I don't
>> know much about either of these items (or Windows for th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 17, 2008, at 09:57 AM, Steve Holden wrote:
>Barry Warsaw wrote:
>[...]
>>
>> I'll note that I plan to hold the beta3 releases until all release
>> blocker and deferred blockers are resolved.
>>
>Ian Ozsvald of ShowMeDo.com noticed a blog pos
On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
bsddb is in a very bad shape, as the 2.6 code hasn't been merged into
3k. I somewhat doubt that this gets resolved before the release, so
bsddb users might need to skip 3.0.
In fact, bsddb as packages in core Python has rarely been in good sh
On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
> On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
>>
>> bsddb is in a very bad shape, as the 2.6 code hasn't been merged into
>> 3k. I somewhat doubt that this gets resolved before the release, so
>> bsddb users might need t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please, no checkins on the 3.0 or 2.6 branches until further notice.
We're a go with the releases tonight. Email is not the quickest way
to get my attention. For that, use irc on freenode, #python-dev.
- -Barry
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 17, 2008, at 10:37 PM, Guido van Rossum wrote:
On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
bsddb is in a very bad shape, as the 2.6 code hasn't been merged
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the second beta releases of Python 2.6 and Python
3.0.
Please note that these are beta releases, and as such are not suitable
for production environments
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The releases have been made, so both the 3.0 branch and the trunk
(2.6) are now open for commits. Remember, there's only one more
planned beta, and we /really/ want to try to hit the October 1st
deadline. Let's do everything we can to stabiliz
On Thu, Jul 17, 2008 at 8:50 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> The releases have been made, so both the 3.0 branch and the trunk (2.6) are
> now open for commits. Remember, there's only one more planned beta, and we
> /really/ want to try to hit the October 1st deadline. Let's do ever
On Thu, Jul 17, 2008 at 7:37 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 17, 2008 at 7:30 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
>> On Jul 17, 2008, at 7:27 PM, Martin v. Löwis wrote:
>>>
>>> bsddb is in a very bad shape, as the 2.6 code hasn't been merged into
>>> 3k. I somewh
24 matches
Mail list logo
