Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12715
| From | Julien Puydt <julien.puydt@gmail.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye |
| Date | 2020-07-05 09:10 +0200 |
| Message-ID | <Ap6WJ-3Yk-1@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <zTC8y-fC-1@gated-at.bofh.it> <Amv5f-27M-1@gated-at.bofh.it> <AnNWa-2KY-7@gated-at.bofh.it> <Ap1u2-v2-1@gated-at.bofh.it> <Ap4UW-2zn-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Le dimanche 05 juillet 2020 à 00:52 -0400, Sandro Tosi a écrit : > Tbh, i think it's time to just rip the bandaid and upload mercurial > python3 to unstable, and deal with the consequences there (i > volunteer to do so); > > What do people think about this? Against band-aid ripping : - breaking other packages is rude ; - sometimes a maintainer doesn't have time to deal with a problem when the problem arises ; For band-aid ripping : - if upstream still doesn't support Python 3 after all those years, the software is probably mostly dead ; - teams make it possible to alleviate personal schedule matters ; - obviously Sandro Tosi tried to help much already : it's not an out- of-the-blue move ; I really don't want to end up supporting Python 2 software without upstream help during a few years -- and that's what will happen if we don't kick Python 2 out before the next release! Cheers, JP
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye Sandro Tosi <morph@debian.org> - 2020-07-05 07:00 +0200 Re: [Python-apps-team] Bug#937009: mercurial: Python2 removal in sid/bullseye Julien Puydt <julien.puydt@gmail.com> - 2020-07-05 09:10 +0200
csiph-web