Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11465

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

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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 leaf, then go all the way back, will take too long, and this is
> IMO unnecessary effort.

I maintain tuna, a leaf package. Upstream is working on the py2->py3 migration.
I expect it to be ready this cycle.  I was planning to replace the py2 deps with
that upstream release.  I can release a stripped down (headless) version in
python3 and I'll do that if my package is going to be removed, but I'd rather
wait for upstream's py3 release.

Can we set dates for removing packages so maintainers can plan what's happening?
I suspect it wouldn't be hard to build a tree from an apt-rdepends graph to set
up a schedule, guaranteeing all traces of python2 are removed by bullseye and
defining the latest possible removal dates for each package in testing.

Stewart Ferguson

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: dropping python2 [was Re: scientific python stack transitions] Stewart Ferguson <stew@ferg.aero> - 2019-07-08 18:30 +0200
  Re: dropping python2 [was Re: scientific python stack transitions] Scott Kitterman <debian@kitterman.com> - 2019-07-09 00:30 +0200
  Re: dropping python2 [was Re: scientific python stack transitions] Rick Thomas <rbthomas@pobox.com> - 2019-07-09 00:30 +0200

csiph-web