Improve the hg-evolve install instructions in the quick-start guide
Nowadays, there's a strong push towards the
$PYTHON -m pip style, and it's possible to do it with a one-liner involving
hg debuginstall, as suggested by @mforbes in this comment in the context of hg-git.
Perhaps a two step approach (first we want to
pip install hg-evolve, followed by if you want to be really sure do this…) is the best way for the reader's learning curve, or perhaps many people would be happy with a correct thing to copy-paste.
We should also document why, despite all habits in the Python development world (and my own practice for years), a direct
pip install with no virtualenv is safe in this case.