-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 16, 2008, at 2:58 PM, Martin v. Löwis wrote:
I think it's definitely too short. Martin has outlined a clean
solution to this
but it's a lot of changes. Let's wait for beta 3.
FWIW, I started writing code today. I couldn't complete it, eit
> I think it's definitely too short. Martin has outlined a clean solution to
> this
> but it's a lot of changes. Let's wait for beta 3.
FWIW, I started writing code today. I couldn't complete it, either (i.e.
it's for 2.6 only, has no docs, and only fixes a single function), but I
hope to submit
> * The ssl changes (Bill, you said you had a separately maintained copy for 3k)
Yes, I think it's all up-to-date.
I'll unblock it after the beta2 release.
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo
On Wed, Jul 16, 2008 at 5:03 PM, nirinA raseliarison
<[EMAIL PROTECTED]> wrote:
> my initial motivation is to make these functions accessible,
> with just a few lines of additionnal code. that's so simple
> with a linux box!
As Daniel Stutzbach already hinted, the easiest way to just get at the
sy
On Wed, Jul 16, 2008 at 11:04 AM, nirinA raseliarison
<[EMAIL PROTECTED]> wrote:
> Daniel Stutzbach wrote:
>> http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/newlib/libm/math/s_erf.c?rev=1.1.1.1&cvsroot=src
>
> a personnal view here. i'm always perplex when there
> are many magic numbers in
On Wed, Jul 16, 2008 at 5:03 PM, nirinA raseliarison
<[EMAIL PROTECTED]> wrote:
> with the gamma from gcc under linux,
> which uses the MPFR library,
Are you sure it uses MPFR? I thought that for gcc 4.3, MPFR was used only for
compile-time constant expressions. For a call to tgamma whose argume
on Tue, 15 Jul 2008 08:32:02 -0500
Daniel Stutzbach wrote:
> I suggest using the versions from newlib's libm. They contain
> extensive comments explaining the math and have a generous license,
> e.g.,:
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/newlib/libm/math/s_erf.c?rev=1.1.1.
From: "nirinA raseliarison" <[EMAIL PROTECTED]>
>>> from test.test_random import gamma
. . .
there is a simple implementation in Python at:
http://en.wikipedia.org/wiki/Lanczos_approximation
with coefficients slightly different from those in
test_random.py, one gets:
. . .
with the gamma from
on Tue, 15 Jul 2008 09:27:39 +0100
Mark Dickinson wrote:
> Writing explicit code for these functions, for platforms
> whose libm doesn't support them, would be a fairly major task.
> Stealing code (in an appropriately legal fashion) from somewhere
> else might work.
> In any case, if you're inter
on Tue, 15 Jul 2008 01:39:19 -0700
Raymond Hettinger wrote:
> In the meantime, here's a little cheat:
>
> >>> from test.test_random import gamma
> >>> gamma(4)
> 5.9982
> >>> gamma(5)
> 24.0
> >>> gamma(6)
> 120.03
> >>> gamma(6.1)
> 142.45194406567856
there is a simple im
On Wed, Jul 16, 2008 at 12:37 AM, Stefan Behnel <[EMAIL PROTECTED]> wrote:
> Nick Coghlan wrote:
>> I recently spent an hour reverting a mistaken CVS checkin (meant to
>> check in one file, checked in the whole working tree instead) that could
>> have been reverted with a single command in SVN.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 15, 2008, at 8:32 AM, Barry Warsaw wrote:
If there is anything you need a decision on, please follow up to
this thread. I'm inundated with email so I can't watch every thread
on the mailing lists. Or ping me on #python-dev.
I'm not cur
I've merged most of the remaining changes to Py3k, with two exceptions:
* The bsddb upgrade (same reason as last time: #2887)
* The ssl changes (Bill, you said you had a separately maintained copy for 3k)
Georg
___
Python-3000 mailing list
Python-3000
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 16, 2008, at 4:41 AM, Antoine Pitrou wrote:
Barry Warsaw python.org> writes:
But 3139 appears important enough to hold up beta 2.
http://bugs.python.org/issue3139
bytearrays are not thread safe
Can we get this fixed by tomorrow? Does any
Hi,
Barry Warsaw python.org> writes:
> But 3139 appears important enough to hold up beta 2.
>
> http://bugs.python.org/issue3139
> bytearrays are not thread safe
>
> Can we get this fixed by tomorrow? Does anybody disagree that we
> should hold up the release for this one? We don't have mu
16 matches
Mail list logo