Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Thomas Goirand
On 7/9/19 12:05 AM, Rick Thomas wrote: > > >> On Jul 8, 2019, at 2:45 PM, Thomas Goirand wrote: >> >> What I did so far: >> debtree -R --rdeps-depth=100 python2.7 >py2.7.deps.dot >> dot -Tsvg -o py2.7.deps.svg py2.7.deps.dot >> >> The result is here: >> http://py2graph.infomaniak.ch/py2.7.deps.s

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Scott Kitterman
On Monday, July 8, 2019 5:45:17 PM EDT Thomas Goirand wrote: > On 7/8/19 6:28 PM, Stewart Ferguson wrote: > > On 2019-07-08 00:13:45, Thomas Goirand wrote: > >> On 7/7/19 5:31 PM, Matthias Klose wrote: > >>> you can start dropping it now, however please don't drop anything yet > >>> with > >>> reve

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Rick Thomas
> On Jul 8, 2019, at 2:45 PM, Thomas Goirand wrote: > > What I did so far: > debtree -R --rdeps-depth=100 python2.7 >py2.7.deps.dot > dot -Tsvg -o py2.7.deps.svg py2.7.deps.dot > > The result is here: > http://py2graph.infomaniak.ch/py2.7.deps.svg Fascinating… Can you give us some hints to i

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Thomas Goirand
On 7/8/19 6:28 PM, Stewart Ferguson wrote: > On 2019-07-08 00:13:45, Thomas Goirand wrote: >> On 7/7/19 5:31 PM, Matthias Klose wrote: >>> you can start dropping it now, however please don't drop anything yet with >>> reverse dependencies. So leaf packages first. >> >> I'm sorry, but I think I nee

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Stewart Ferguson
On 2019-07-08 00:13:45, Thomas Goirand wrote: > On 7/7/19 5:31 PM, Matthias Klose wrote: >> you can start dropping it now, however please don't drop anything yet with >> reverse dependencies. So leaf packages first. > > I'm sorry, but I think I need to contest this. Doing things in order, > first

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Thomas Goirand
On 7/8/19 10:10 AM, Ansgar wrote: > Thomas Goirand writes: >> On 7/7/19 5:31 PM, Matthias Klose wrote: >>> you can start dropping it now, however please don't drop anything yet with >>> reverse dependencies. So leaf packages first. >> >> I'm sorry, but I think I need to contest this. Doing things

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Elena ``of Valhalla''
On 2019-07-08 at 07:16:01 +, PICCA Frederic-Emmanuel wrote: > it would be nice, if the python2 packages could be skipped in bulleye but not > for backports in buster. > > Is it something which could be envision ? I don't think it would be accepted by backports, since it goes against the requ

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Ansgar
Thomas Goirand writes: > On 7/7/19 5:31 PM, Matthias Klose wrote: >> you can start dropping it now, however please don't drop anything yet with >> reverse dependencies. So leaf packages first. > > I'm sorry, but I think I need to contest this. Doing things in order, > first leaf, then go all the w

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Andrey Rahmatullin
On Mon, Jul 08, 2019 at 07:16:01AM +, PICCA Frederic-Emmanuel wrote: > it would be nice, if the python2 packages could be skipped in bulleye but not > for backports in buster. > > Is it something which could be envision ? Not in the main backports, maybe in -sloppy. And it will be hard or imp

RE:dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread PICCA Frederic-Emmanuel
it would be nice, if the python2 packages could be skipped in bulleye but not for backports in buster. Is it something which could be envision ? Fred

Re: dropping python2 [was Re: scientific python stack transitions]

2019-07-08 Thread Thomas Goirand
On 7/8/19 12:27 AM, Scott Kitterman wrote: > Are you 100% certain that there isn't some small subset of python2 packages > we > will end up needing for bullseye? I'm 100% certain that we should as much as possible avoid this, indeed. I'm also convinced we should do our best to speed-up the Pytho