Re: Python 2 removal and thg packaging status

Hi there, It's been a few months, and Python 3 Windows support is in much better shape than it used to. The CI is still flaky, but at least we've got a decent coverage of core Mercurial. Greg, what's the status regarding thg packaging? Next release cycle (6.1) will remove Python 3 support

Re: Python 2 removal and thg packaging status

My plan of attack was to implement support for packaging in PyOxidizer and have thg (and Mercurial) use this functionality (with or without the traditional PyOxidizer-building-the-binary approach). However, I've been sidetracked by various things. Ugh, COVID. I'll try to take a look at what

Re: Python 2 removal and thg packaging status

> On Apr 3, 2021, at 6:34 PM, Matt Harbison wrote: > > On Sat, Apr 3, 2021 at 12:18 PM Raphaël Gomès > wrote: >> >> Hello all, >> >> As you all know, Mercurial's codebase is still burdened by Python 2 >> support. Patches still >> need to be adapted for

Re: Python 2 removal and thg packaging status

On Sat, Apr 3, 2021 at 12:18 PM Raphaël Gomès wrote: > > Hello all, > > As you all know, Mercurial's codebase is still burdened by Python 2 > support. Patches still > need to be adapted for backwards compat, some Python niceties still > cannot be used, > and the Heptapod CI which is used on a

Re: Python 2 removal and thg packaging status

+ CC actually Greg, oops On 4/3/21 6:18 PM, Raphaël Gomès wrote: Hello all, As you all know, Mercurial's codebase is still burdened by Python 2 support. Patches still need to be adapted for backwards compat, some Python niceties still cannot be used, and the Heptapod CI which is used on a

Python 2 removal and thg packaging status

Hello all, As you all know, Mercurial's codebase is still burdened by Python 2 support. Patches still need to be adapted for backwards compat, some Python niceties still cannot be used, and the Heptapod CI which is used on a near majority of the patches we collectively land is still putting