<story><title>Unladen Swallow is dead</title><url>http://groups.google.com/group/unladen-swallow/msg/bd4e6f935c23252a</url><text></text></story><parent_chain></parent_chain><comment><author>jnoller</author><text>No, it&apos;s not dead, and I&apos;m sad that this is sitting at the front page, because it&apos;s so misleading.&lt;p&gt;The fact is, it&apos;s stalled (&lt;a href=&quot;https://www.google.com/buzz/bcannon/bZDN1jNZ3uC/Is-this-finally-going-to-push-CPython-into-the&quot; rel=&quot;nofollow&quot;&gt;https://www.google.com/buzz/bcannon/bZDN1jNZ3uC/Is-this-fina...&lt;/a&gt;) - &lt;a href=&quot;http://www.python.org/dev/peps/pep-3146/&quot; rel=&quot;nofollow&quot;&gt;http://www.python.org/dev/peps/pep-3146/&lt;/a&gt; was accepted. This means that a branch was made with the intent of merging US into Py3k. Unfortunately, this proved to be a greater task then originally planned. Stalled != Dead.&lt;p&gt;To quote Collin:
&quot;&lt;i&gt;Unladen Swallow is stalled because merging the code into the py3k-jit branch plain sucks: lots of new compatibility work to be done, lots of corners we had to un-cut, lots of drudge and suffering. It doesn&apos;t help that Google is full of far more interesting and influential projects.&lt;/i&gt;&quot;&lt;p&gt;So add in the fact that the resources Google had &quot;assigned&quot; to the project got moved/reassigned onto something else, and what you have is a very stalled project. Collin has stated that they hope(d) that other python-core devs would/will step up to help, but everyone is pretty tapped out as it is.&lt;p&gt;I&apos;m as disappointed as anyone that it&apos;s stalled - given it&apos;s compatibility with C extensions, potential speedups and future potential, it has been one of the projects I&apos;ve had the most hope for.&lt;p&gt;That said, PyPy is also coming along; when they hit 2.7 compatibility and they have drop-in replacement capability, the ecosystem will be &lt;i&gt;very&lt;/i&gt; interesting. Competition in the interpreter space is &lt;i&gt;good&lt;/i&gt;, and I feel that Unladen&apos;s aggressiveness helped spur/move PyPy along.&lt;p&gt;That said Unladen (in my mind) remains the CPython interpreter&apos;s best way of moving into the future. It still has the most promise for &lt;i&gt;that&lt;/i&gt; code base.</text></comment>
<story><title>Unladen Swallow is dead</title><url>http://groups.google.com/group/unladen-swallow/msg/bd4e6f935c23252a</url><text></text></story><parent_chain></parent_chain><comment><author>cawhitworth</author><text>Reading the thread, it seems there&apos;s still an intention to roll the JIT into py3k at some point, but the project devs don&apos;t have the time and the community doesn&apos;t seem to have the inclination to take over the work. I think calling it dead might be overstating things slightly.&lt;p&gt;Or, seeing as this is Python we&apos;re talking about: It&apos;s not dead, it&apos;s just resting.</text></comment>