Next steps in PyPy investigations

Jun Wu quark at fb.com
Fri Feb 12 10:31:49 EST 2016


As being worked on chg for a while, I would say threads are not the way
to go for mainly 2 reasons:

1. Users can no longer press Ctrl+C to stop a hang command without
    affecting other chg clients, which I think is a deal breaker.
2. Python is such a language that you can do crazy things in
    extensions. chg is *much* better staying stateless for correctness.
    For example, there is a global variable in blackbox.

If we need some persistent data held in memory, a dedicated daemon
with cleanly defined interface is much better imo, although IPC has
some overheads.


On 02/12/2016 12:42 AM, Bryan O'Sullivan wrote:
> On the simplest level, tweaking chg to use threads instead of forking is
> just a one-liner.


More information about the Mercurial-devel mailing list