Speaking as a maintainer of Mercurial and an avid user of Python, I feel like the experience of making Mercurial work with Python 3 is worth sharing because there are a number of lessons to be learned.

This post is logically divided into two sections: a mostly factual recount of Mercurial’s Python 3 porting effort and a more opinionated commentary of the transition to Python 3 and the Python language ecosystem as a whole. Those who don’t care about the mechanics of porting a large Python project to Python 3 may want to skip the next section or two

source: L

This page describes the plan and status for leveraging the Rust programming language in Mercurial.

Quite a bit more ambitious than rewriting a few C extensions, with accompanying difficulties.

source: L

The fundamental difference between the monorepo and multirepo philosophies boils down to a difference about what will allow teams working together on a system to go fastest.

source: L

For years, Mercurial has included various commands that allow history modification: rebase, histedit, commit --amend and so forth. However, there’s a catch: until now, Mercurial’s various mechanisms for modifying history have been unsafe, in that changesets were destroyed (“stripped”) rather than simply hidden and still easy to recover. evolve makes things better by changing the behaviour of most existing history modification commands so they use a safer mechanism (changeset obsolescence, covered below) rather than the older, less safe strip operation.

If you really must fix history, a better way.

source: L