pycompat.py strategy

Joerg Sonnenberger joerg at bec.de
Tue Feb 22 22:06:16 UTC 2022


Am Mon, Feb 21, 2022 at 11:47:36AM -0700 schrieb Gregory Szorc:
> Some options:
> 
> a) Attempt to delete as much as pycompat.py as possible (leaving only the
> pieces needed to abstract over differences in Python 3.5-3.x).
> b) Leave the ~complete API provided by pycompat.py and delete pycompat
> usage within the repo as much as possible.
> c) Leave the ~complete API provided by pycompat.py and still use pycompat
> heavily within the repo.

Personally, I'd prefer to start with (c) and gradually go to (b).

Joerg



More information about the Mercurial-devel mailing list