[Python-apps-team] Bug#937009: Bug#937009: mercurial: Python2 removal in sid/bullseye

[Sandro Tosi]

Hello Julien,

On Tue, Feb 18, 2020 at 12:33 PM Julien Cristau <jcristau at debian.org> wrote:
> Before switching in sid I'd want to:
> - be able to use the python3 version myself
> - give extensions some time to figure out their own switch
> - ideally not regress significant functionality; e.g. python-subversion
>   is still not available for python3
>
> I don't know what that means in terms of timeframe, it may or may not
> happen in time for bullseye, but I'm also not in a rush and I'd rather
> not break stuff by switching too early.

I see that python3-enabled mercurial has been in experimental for a 3
weeks now, how's it going? it would greatly help progress with the
overall py2removal effort if we could start planning to upload that
mercurial release to sid.

Can you share with us your plans here?

I understand and agree (in general) with your desire to now break
anything, but we're also at the tail end of the py2removal process, so
we are at a point where something may be broken, for some period of
time.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi