pycompat.py strategy
Raphaël Gomès
raphael.gomes at octobus.net
Tue Mar 1 10:20:41 UTC 2022
On 2/22/22 23:06, Joerg Sonnenberger wrote:
> 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).
Care to elaborate? :)
> Joerg
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
More information about the Mercurial-devel
mailing list