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


Groups > linux.debian.maint.python > #11799 > unrolled thread

Re: should Debian add itself to https://python3statement.org ?

Started byIan Jackson <ijackson@chiark.greenend.org.uk>
First post2019-09-12 17:10 +0200
Last post2019-09-12 18:30 +0200
Articles 3 — 3 participants

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: should Debian add itself to https://python3statement.org  ? Ian Jackson <ijackson@chiark.greenend.org.uk> - 2019-09-12 17:10 +0200
    Re: should Debian add itself to https://python3statement.org ? Matthias Klose <doko@debian.org> - 2019-09-12 18:10 +0200
    Re: should Debian add itself to https://python3statement.org ? Paul Gevers <elbrus@debian.org> - 2019-09-12 18:30 +0200

#11799 — Re: should Debian add itself to https://python3statement.org ?

FromIan Jackson <ijackson@chiark.greenend.org.uk>
Date2019-09-12 17:10 +0200
SubjectRe: should Debian add itself to https://python3statement.org ?
Message-ID<yFyTo-7Cg-13@gated-at.bofh.it>
Drew Parsons writes ("should Debian add itself to https://python3statement.org  ?"):
> https://python3statement.org/ is a site documenting the projects which 
> are supporting the policy of dropping Python2 to keep Python3 only.

That statement is a *pledge* to drop support for python2 by the end of
2020.  Have we in fact made such a pledge ?  I think I may have missed
the memo that python2 would be removed from bullseye.

I did some searching and found this
  https://lists.debian.org/debian-python/2019/07/msg00080.html
which is a sane-looking transition plan but doesn't seem to have a
timeframe and doesn't seem to contemplate removal of the actual
python2 interpreter.

FTAOD I don't have an opinion about whether bullseye *should* ship
without python2.  Obviously dropping it would not be desirable from
users' pov, but maintaining an ancient thing by ourselves would not be
desirable either.  I think I trust the Debian Python team to make that
tradeoff.

But we need to be clear what's going on and communicate early.  If
python2 is going out of bullseye then there are a lot of bugs that
should probably be marked rc fairly soon...

thanks,
Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

[toc] | [next] | [standalone]


#11801 — Re: should Debian add itself to https://python3statement.org ?

FromMatthias Klose <doko@debian.org>
Date2019-09-12 18:10 +0200
SubjectRe: should Debian add itself to https://python3statement.org ?
Message-ID<yFzPr-8ec-3@gated-at.bofh.it>
In reply to#11799
On 12.09.19 17:01, Ian Jackson wrote:
> Drew Parsons writes ("should Debian add itself to https://python3statement.org  ?"):
>> https://python3statement.org/ is a site documenting the projects which
>> are supporting the policy of dropping Python2 to keep Python3 only.
> 
> That statement is a *pledge* to drop support for python2 by the end of
> 2020.  Have we in fact made such a pledge ?  I think I may have missed
> the memo that python2 would be removed from bullseye.
> 
> I did some searching and found this
>    https://lists.debian.org/debian-python/2019/07/msg00080.html
> which is a sane-looking transition plan but doesn't seem to have a
> timeframe and doesn't seem to contemplate removal of the actual
> python2 interpreter.
> 
> FTAOD I don't have an opinion about whether bullseye *should* ship
> without python2.  Obviously dropping it would not be desirable from
> users' pov, but maintaining an ancient thing by ourselves would not be
> desirable either.  I think I trust the Debian Python team to make that
> tradeoff.
> 
> But we need to be clear what's going on and communicate early.  If
> python2 is going out of bullseye then there are a lot of bugs that
> should probably be marked rc fairly soon...

it's communicated here:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=py2removal;users=debian-python@lists.debian.org

derived from
https://release.debian.org/transitions/html/python2-rm.html (not perfect, we are 
still missing bug reports).


it's way too early to mark all of these as RC.

No, it's not yet decided if Python2 will be part of bullseye.  But the python 
command and the unversioned python packages won't be part of bullseye.



> 
> thanks,
> Ian.
> 

[toc] | [prev] | [next] | [standalone]


#11802 — Re: should Debian add itself to https://python3statement.org ?

FromPaul Gevers <elbrus@debian.org>
Date2019-09-12 18:30 +0200
SubjectRe: should Debian add itself to https://python3statement.org ?
Message-ID<yFA8O-8lq-15@gated-at.bofh.it>
In reply to#11799

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

Hi,

On 12-09-2019 17:01, Ian Jackson wrote:
> But we need to be clear what's going on and communicate early.

Yes, not on the front page, but there is (first bullet):

https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#deprecated-components

Paul

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web