Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #996268
| From | Julien Cristau <jcristau@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#937009: mercurial: Python2 removal in sid/bullseye |
| Date | 2020-02-18 18:40 +0100 |
| Message-ID | <zBf0J-7DI-5@gated-at.bofh.it> (permalink) |
| References | <yPGcV-4GM-7@gated-at.bofh.it> <yXiGu-3Wi-5@gated-at.bofh.it> <yPGcV-4GM-7@gated-at.bofh.it> <yXiGu-3Wi-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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. Cheers, Julien
Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#937009: mercurial: Python2 removal in sid/bullseye Julien Cristau <jcristau@debian.org> - 2020-02-18 18:40 +0100 Bug#937009: mercurial: Python2 removal in sid/bullseye Andrej Shadura <andrewsh@debian.org> - 2020-03-01 15:10 +0100
csiph-web