From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Python 2.7 end of life on January 1, 2020
Date: Sat, 02 Mar 2019 21:12:53 +0100 [thread overview]
Message-ID: <87ef7pkpbu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190301195404.1c00356b@windsurf> (Thomas Petazzoni's message of "Fri, 1 Mar 2019 19:54:04 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> Through a LWN.net article, I recently realized that Python 2.7 will see
> its end of life on January 1, 2020, according to:
> https://www.python.org/dev/peps/pep-0373/
> You also have a fancy countdown at:
> https://pythonclock.org/
> This means that our 2020.02 LTS release probably should not have Python
> 2.x anymore ?
Yes, it is too late to change for 2019.02, but 2020.02 should probably
not include it unless somebody else steps up and maintains it when it
goes EOL.
> If that's our decision, then we should probably discuss the deprecation
> path we want to follow to strongly warn users that they should migrate
> away from Python 2.x.
Hasn't that been the published statement by the upstream Python
developers ever since 3.x was released 10 years ago? I am not sure what
else we could/should do, besides perhaps mentioning it in the 2019.02
release notes?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-02 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 18:54 [Buildroot] Python 2.7 end of life on January 1, 2020 Thomas Petazzoni
2019-03-02 7:58 ` Bernd Kuhls
2019-03-02 20:12 ` Peter Korsgaard [this message]
2019-03-04 7:20 ` Arnout Vandecappelle
2019-03-04 13:05 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef7pkpbu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox