Next steps in PyPy investigations

Bryan O'Sullivan bos at serpentine.com
Thu Feb 11 16:59:45 UTC 2016


On Thu, Feb 11, 2016 at 7:30 AM, Laurent Charignon <lcharignon at fb.com>
wrote:

> I didn't really follow the discussions around pypy, when are we planning
> to support pypy?
>

Pierre-Yves has agreed with the PyPy development team on a contract, funded
by Facebook, to perform some more work on PyPy and Mercurial.

The scope to begin with is quite narrow:

Get the Mercurial test suite completely passing. A handful of
revset-related tests require some fixes to some bad assumptions that the
revset machinery makes.

See what easyish optimizations can be added or improved to further speed up
the performance of some core Mercurial commands. This may involve porting
some C extensions to work with cffi, which will imminently force us to
think harder about the question of C data structures.

Look at how to reduce or otherwise make invisible the PyPy JIT startup and
warmup time. Now that chg is about to arrive in core Mercurial, that will
presumably be the most obvious path to follow.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160211/4be1b8ee/attachment.html>


More information about the Mercurial-devel mailing list