Hi Andrej! On Fri, Feb 14, 2020 at 03:17:07PM +0100, Andrej Shadura wrote: > On Thu, 30 Jan 2020 12:08:33 +0300 Dmitry Shachnev <mity...@debian.org> wrote: > > setuptools-scm has removed Python 2 support (see #938470), so python-keyring > > build-dependencies are no longer satisfiable. > > It has since been reintroduced.
You are right, setuptools-scm has been reintroduced, so I am not removing Python 2 support from python-keyring for now. > > Thus I am going to remove Python 2 support from python-keyring, so I am > > bumping severity of this bug. That support will be removed in 10 days from > > now, on some day after 2020-02-09. > > > > I am also CCing the maintainers of packages which are listed as blockers of > > this bug (mercurial and mercurial-extension-utils). > > Well, it would break this package, so you need to wait until Mercurial > switches to Python 3. It is very sad that #937009 got the py2keep tag, and the last two questions got no reply. Do you know anything about the status of mercurial Python 2 migration? Upstream now officially supports Python 3, but the developer “anticipates a long tail of random bugs” according to [1]. However, there is still a lot of time to fix those bugs before Bullseye freeze, so in my opinion that does not deserve a py2keep tag. Maybe better to do a switch earlier to increase the period for reporting and fixing bugs? [1]: https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journey-to-and-reflections-on-python-3/ -- Dmitry Shachnev
signature.asc
Description: PGP signature
