On Tue, 18 Feb 2020 18:31:50 +0100 Julien Cristau <jcris...@debian.org> wrote: > On Thu, Oct 31, 2019 at 02:25:22PM +0100, Matthias Klose wrote: > > Julian, you added the py2keep tag. Reading the upstream mail for the 5.2 > > release, it looks like the release will happen next month. So why keeping > > it as Python2 version for the bullseye release? > > 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 would be great if you could ship Mercurial as dual Python 2 + Python 3 package but with /usr/bin/hg being Python 2, so that users can try the Python 3 version and extensions can be used with either. As it is now, it’s not possible e.g. to ship TortoiseHg at all since it needs core Mercurial modules in Python 3 (since Python 2 dependencies it might use have already been removed). -- Cheers, Andrej