I've been busy with other work for Google, but I'm hoping to get some
time to push further on the upstream migration of Unladen Swallow into
CPython. We're still targeting CPython 3.3, though we may not get into
the cycle as early as we would have liked.
Jeffrey and I have been pulled on to other projects of higher
importance to Google. Unfortunately, no-one from the Python
open-source community has been interested in picking up the merger
work, and since none of the original team is still full-time on the
project, it's moving very slowly. Finishing up the merger into the
py3k-jit branch is a high priority for me this quarter, but what
happens then is an open question.
On Tue, Nov 9, 2010 at 9:48 AM, garyrob <grob...@flyfi.com> wrote:
>> Finishing up the merger into the
>> py3k-jit branch is a high priority for me this quarter, but what
>> happens then is an open question.
> Does that mean there is no longer a commitment to merging the JIT into
> Python 3.2 -- or are you saying that WILL be done this quarter?
I need to get the code from the Unladen Swallow repository moved into
the python.org svn repo's py3k-jit branch. There are still a number of
issues that need work before final merger into Python 3.x is approved;
the final merger is contingent on resolving the remaining issues in
PEP 3146. The Python community will need to help resolve these
That hasn't been on the table for quite some time. The deadline for
new features in 3.2 is some time in the next few weeks.
Am 08.11.2010 17:48, schrieb Collin Winter:
> Jeffrey and I have been pulled on to other projects of higher
> importance to Google. Unfortunately, no-one from the Python
> open-source community has been interested in picking up the merger
> work, [...]
I think it's very unfortunate that Google does not seem to be committed
on getting the JIT into Python trunk. I think most of the python-dev
community does not believe it's worth the effort, especially as Google
did not seem to have picked up U-S for internal use (Youtube?).
Although my free time diminished quite a bit, I'm still willing to
commit time to U-S and/or jit-3k, but it seems a bit pointless if I'm
the only one working on that. Especially since I'm locked to python2.x
for the time being (maybe I should work on Numpy/Scipy instead?)
On Fri, Dec 10, 2010 at 08:47, disappearedng <disapp...@gmail.com> wrote:
> This is sad.
Yes, submit them to bugs.python.org.
> Also, where does
> Unladen live these days? Is it still in this Google Code repo, or is
> it somewhere else?
Depends on which version. The released stuff that Collin and friends
did is still there. But the merging work is being done in the py3k-jit
branch at svn.python.org.
> My fear is that it takes someone with more knowledge to do these
> things, but I'm willing to at least try to help.
That I have no idea, but you can always ask for help.