[Python-3000] Py3k release schedule worries (original) (raw)
Adam Olsen rhamph at gmail.com
Tue Dec 19 23:52:28 CET 2006
- Previous message: [Python-3000] Efficient LC's which don't leak the iteration variables (was Re: Py3k release schedule worries)
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/18/06, Guido van Rossum <guido at python.org> wrote:
character, but AFAICT it fizzled; nobody has proposed to help with getting the int unification branch, which is mostly done but still has 22 failing tests last time I looked. I've received a few contributions
I'd also like to see people volunteer to help with the implementation of some of these projects, and with the implementation of projects that already have a PEP or don't need one. For example:
- finishing the int unification branch
Who should I conspire with to get this done? I've already tracked down one of the bugs: convert_to_double in floatobject.c prefers PyInt_AS_LONG, assuming it can't fail, which is no longer true.
5.0 * 9999999999999 -5.0 1.0 + 999999999999 0.0
What is the policy on working on the p3yk branch? I thought I read that we should skip bug reports, but I've been unable to find the email saying so.
-- Adam Olsen, aka Rhamphoryncus
- Previous message: [Python-3000] Efficient LC's which don't leak the iteration variables (was Re: Py3k release schedule worries)
- Next message: [Python-3000] Py3k release schedule worries
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]