Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11484
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: <DKIM> Re: dropping python2 [was Re: scientific python stack transitions] |
| Date | 2019-07-17 02:50 +0200 |
| Message-ID | <ykGiR-6NN-5@gated-at.bofh.it> (permalink) |
| References | (8 earlier) <ykxfz-1wu-21@gated-at.bofh.it> <ykxfz-1wu-17@gated-at.bofh.it> <ykxyV-1CF-5@gated-at.bofh.it> <ykxSh-1J9-3@gated-at.bofh.it> <ykxSh-1J9-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On July 16, 2019 3:42:47 PM UTC, Matthias Klose <doko@debian.org> wrote: >On 16.07.19 17:31, Julien Puydt wrote: >> Le 16/07/2019 à 17:21, Andrey Rahmatullin a écrit : >>> Python 2 is included in buster and so will be supported for several >>> years. >>> >> >> The starting point of the thread was : >> 1. Ok, buster has Python 2 so even if upstream drops it, we will >still >> support it for the years to come for our users ; >> 2. but the next stable will come out after upstream has EOL-ed Python >2, >> so we must kick it out as soon as possible from testing+unstable, > >> because there's no way we'll support Python 2 in that next stable! > >no, that's your interpretation, not mine. If an important enough >application >still needs it, we should ship it. I completely agree. The reason I put in for a tracker is to make it easier to see where people can focus to start burning down the stack. Not because I am confident we'll get there this cycle. Scott K
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
dropping python2 [was Re: scientific python stack transitions] Drew Parsons <dparsons@debian.org> - 2019-07-07 17:00 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Matthias Klose <doko@debian.org> - 2019-07-07 17:40 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Drew Parsons <dparsons@debian.org> - 2019-07-07 19:30 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Scott Kitterman <debian@kitterman.com> - 2019-07-08 00:40 +0200
RE:dropping python2 [was Re: scientific python stack transitions] PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2019-07-08 09:40 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Andrey Rahmatullin <wrar@debian.org> - 2019-07-08 09:50 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Elena ``of Valhalla'' <valhalla-d@trueelena.org> - 2019-07-08 10:20 +0200
Re: dropping python2 [was Re: scientific python stack transitions] "W. Martin Borgert" <debacle@debian.org> - 2019-07-09 22:50 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Ansgar <ansgar@debian.org> - 2019-07-08 10:20 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Paul Tagliamonte <paultag@debian.org> - 2019-07-16 17:10 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Andrey Rahmatullin <wrar@debian.org> - 2019-07-16 17:30 +0200
Re: <DKIM> Re: dropping python2 [was Re: scientific python stack transitions] Matthias Klose <doko@debian.org> - 2019-07-16 17:50 +0200
Re: <DKIM> Re: dropping python2 [was Re: scientific python stack transitions] Scott Kitterman <debian@kitterman.com> - 2019-07-17 02:50 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Matthias Klose <doko@debian.org> - 2019-07-16 17:30 +0200
Re: dropping python2 [was Re: scientific python stack transitions] Paul Tagliamonte <paultag@debian.org> - 2019-07-16 17:50 +0200
csiph-web