-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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.
Working on the 3.0 port just now. 03:40 in the
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
-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
-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
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
> 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
> 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-Dev mailing list
Python-Dev
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
> 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
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
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 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
-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_multiprocessing hangs intermittently on POSIX platforms
3375 _multiprocessing.so build pro
13 matches
Mail list logo
