From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] python: move to staging
Date: Fri, 25 Oct 2019 09:28:27 +0200 [thread overview]
Message-ID: <20191025072827.GD30823@pengutronix.de> (raw)
In-Reply-To: <20190925130825.19498-1-rhi@pengutronix.de>
On Wed, Sep 25, 2019 at 03:08:25PM +0200, Roland Hieber wrote:
> Use of Python 2 has been widely discouraged [citation needed], and
> remaining users should start migrating to Python 3 [1]. Prepare for
> Python 2 End-of-Life, which is in about three months from now [2].
>
> [1]: https://www.python.org/dev/peps/pep-0404/#id13
> [2]: https://pythonclock.org/
I don't think that we're quite there yet. But it is something to keep in
mind.
Also, there are several more packages that select python.
Michael
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> rules/python-imaging.in | 7 ++++++-
> rules/python-protobuf.in | 6 +++++-
> rules/python-pyro.in | 7 ++++++-
> rules/python-routing.in | 7 ++++++-
> rules/python-rplicmp.in | 7 ++++++-
> rules/python.in | 7 ++++++-
> 6 files changed, 35 insertions(+), 6 deletions(-)
>
> diff --git a/rules/python-imaging.in b/rules/python-imaging.in
> index c64d79e74438..1f5bf963866d 100644
> --- a/rules/python-imaging.in
> +++ b/rules/python-imaging.in
> @@ -1,4 +1,6 @@
> -## SECTION=python
> +## SECTION=staging
> +## old section:
> +### SECTION=python
>
> menuconfig PYTHON_IMAGING
> tristate
> @@ -10,6 +12,9 @@ menuconfig PYTHON_IMAGING
> help
> FIXME
>
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> +
> if PYTHON_IMAGING
>
> config PYTHON_IMAGING_FREETYPE
> diff --git a/rules/python-protobuf.in b/rules/python-protobuf.in
> index b22bc715c8e2..bc41cf9a192c 100644
> --- a/rules/python-protobuf.in
> +++ b/rules/python-protobuf.in
> @@ -1,4 +1,6 @@
> -## SECTION=python
> +## SECTION=staging
> +## old section:
> +### SECTION=python
>
> config PYTHON_PROTOBUF
> tristate
> @@ -11,3 +13,5 @@ config PYTHON_PROTOBUF
> efficient yet extensible format.
> This package contains the Python bindings for protobuf.
>
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> diff --git a/rules/python-pyro.in b/rules/python-pyro.in
> index 83e6ab94785e..a14565ee77fb 100644
> --- a/rules/python-pyro.in
> +++ b/rules/python-pyro.in
> @@ -1,4 +1,6 @@
> -## SECTION=python
> +## SECTION=staging
> +## old section:
> +### SECTION=python
>
> config PYTHON_PYRO
> tristate
> @@ -18,3 +20,6 @@ config PYTHON_PYRO
> that enables you to build distributed applications rapidly and
> effortlessly. Pyro is written in 100% pure Python and therefore
> runs on many platforms and Python versions, including Python 3.x
> +
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> diff --git a/rules/python-routing.in b/rules/python-routing.in
> index 5a2c62aaadc4..a59cab8a793d 100644
> --- a/rules/python-routing.in
> +++ b/rules/python-routing.in
> @@ -1,4 +1,6 @@
> -## SECTION=python
> +## SECTION=staging
> +## old section:
> +### SECTION=python
>
> config PYTHON_ROUTING
> tristate
> @@ -12,3 +14,6 @@ config PYTHON_ROUTING
> was written to encompass the "route" module which isn't encompassed
> by any other libnl3 python binding. The special route module is
> necessary for the simpleRPL implementation.
> +
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> diff --git a/rules/python-rplicmp.in b/rules/python-rplicmp.in
> index 75fedc5098b4..dbf556d372a0 100644
> --- a/rules/python-rplicmp.in
> +++ b/rules/python-rplicmp.in
> @@ -1,4 +1,6 @@
> -## SECTION=python
> +## SECTION=staging
> +## old section:
> +### SECTION=python
>
> config PYTHON_RPLICMP
> tristate
> @@ -9,3 +11,6 @@ config PYTHON_RPLICMP
> help
> This module allows easy creation of ICMPv6 socket in Python tailored to
> send RPL messages.
> +
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> diff --git a/rules/python.in b/rules/python.in
> index 75390188876e..d0fbc69be43b 100644
> --- a/rules/python.in
> +++ b/rules/python.in
> @@ -1,4 +1,6 @@
> -## SECTION=scripting_languages
> +## SECTION=staging
> +## old section:
> +### SECTION=scripting_languages
>
> menuconfig PYTHON
> tristate "python "
> @@ -25,6 +27,9 @@ menuconfig PYTHON
> comes with extensive standard libraries, and
> can be learned in a few days.
>
> + STAGING: remove in PTXdist 2020.10.0 due to Python 2 End-of-Life:
> + <https://www.python.org/dev/peps/pep-0373/>.
> +
> if PYTHON
>
> config PYTHON_NCURSES
> --
> 2.23.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-10-25 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 13:08 Roland Hieber
2019-10-25 7:28 ` Michael Olbrich [this message]
2020-04-29 16:23 ` [ptxdist] [PATCH v2] " Roland Hieber
2020-05-07 8:12 ` Michael Olbrich
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=20191025072827.GD30823@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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