I wanted to know about the current status of Unladen-Swallow project. The project page describes milestones only till 2009. Also, has the PEP 3146 been accepted by BDFL and the python community and what is the timeline for the merging of Unladen-Swallow with the Python 3k branch?
On Fri, Sep 10, 2010 at 4:27 PM, Swapnil Talekar <swapnil...@gmail.com> wrote: > Hello, > I wanted to know about the current status of Unladen-Swallow project. The > project page describes milestones only till 2009. > Also, has the PEP 3146 been accepted by BDFL and the python community and > what is the timeline for the merging of > Unladen-Swallow with the Python 3k branch?
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.
Please please please do not let us get swamped. It is a really
exciting development. I use python a lot and would like to see it gain
momentum against competitors like scala or even c++.
On Mon, Nov 8, 2010 at 1:10 AM, Arek Stefański <asmaged...@gmail.com> wrote: > Hey, I thought Unladen Swallow is dead. > Sure seems close to this. > It's really cool project, why is it so 'abandoned' right now? :<
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 Mon, Nov 8, 2010 at 1:10 AM, Arek Stefański <asmaged...@gmail.com> wrote:
> > Hey, I thought Unladen Swallow is dead.
> > Sure seems close to this.
> > It's really cool project, why is it so 'abandoned' right now? :<
> 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 <grobin...@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 problems.
> On Nov 8, 11:48 am, Collin Winter <collinwin...@google.com> wrote: >> Hi Arek,
>> On Mon, Nov 8, 2010 at 1:10 AM, Arek Stefański <asmaged...@gmail.com> wrote: >> > Hey, I thought Unladen Swallow is dead. >> > Sure seems close to this. >> > It's really cool project, why is it so 'abandoned' right now? :<
>> 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 12:48 PM, garyrob <grobin...@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?
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.
> 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?)
You might want to check out PyPy. They seem to be gaining momentum and
just released 1.4. Their JIT is getting great performance, sometimes
close to C++ speed.
On Nov 10, 4:48 pm, Jörg Blank <e...@4geeks.de> wrote:
> > 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 Mon, Nov 8, 2010 at 1:10 AM, Arek Stefański <asmaged...@gmail.com> wrote:
> > Hey, I thought Unladen Swallow is dead.
> > Sure seems close to this.
> > It's really cool project, why is it so 'abandoned' right now? :<
> 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.
Just to remind everyone who wishes to see Unladen merged into Python 3, help is needed (and welcomed!) to see it happening. You can see the todo list at http://svn.python.org/view/python/branches/py3k-jit/JIT_TODO.txt?view... and see if you can help write patches to merge the changes from Unladen into Python itself or the Unladen branch of Python 3.
On Wed, Jan 5, 2011 at 02:52, John Szakmeister <j...@szakmeister.net> wrote: > On Sat, Dec 11, 2010 at 2:43 PM, Brett Cannon <br...@python.org> wrote: >> Just to remind everyone who wishes to see Unladen merged into Python >> 3, help is needed (and welcomed!) to see it happening. You can see the >> todo list at http://svn.python.org/view/python/branches/py3k-jit/JIT_TODO.txt?view... >> and see if you can help write patches to merge the changes from >> Unladen into Python itself or the Unladen branch of Python 3.
> How does an ordinary (non-committer) go about doing that? Writing > patches and submitting them via the bug tracker?
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.
