[Python-3000] Py3k release schedule worries

Adam Olsen rhamph at gmail.com
Tue Dec 19 23:52:28 CET 2006

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
>>> 1.0 + 999999999999

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

More information about the Python-3000 mailing list