mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2] python: move to staging
Date: Thu, 7 May 2020 10:12:12 +0200	[thread overview]
Message-ID: <20200507081212.GB1153@pengutronix.de> (raw)
In-Reply-To: <20200429162338.6178-1-rhi@pengutronix.de>

On Wed, Apr 29, 2020 at 06:23:38PM +0200, Roland Hieber wrote:
> Use of Python 2 has been widely discouraged for some years [citation
> needed], and remaining users should start migrating to Python 3 [1].
> Move Python 2 to staging to reflect that.
> 
> [1]: https://www.python.org/dev/peps/pep-0404/#id13

I'd like to keep the around a little bit longer. We have alot of other
stuff that is dead or eol for much longer. Also:
1. removing the dependencies on system python2 are a lot more important
   because old ptxdist versions are often used for a long time. So if
   removing Python2 is your goal, then you should start there.
2. You need to move all python2 packages to staging as well and add
   dependencies to all suboptions. There must be no dependency conflicts
   when STAGING is disabled.

Regards,
Michael

> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> 
> --
> v2:
>  - adapt removal date after final python v2.7.18 release
>  - only move the python package for now. all reverse dependencies will
>    depend on STAGING for now; we can find out later whether they build
>    with python3 too.
> ---
>  rules/python.in | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/rules/python.in b/rules/python.in
> index 75390188876e..7afc622b9786 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 2021.05.0 due to Python 2 End-of-Life:
> +	  <https://mail.python.org/archives/list/python-announce-list@python.org/thread/OFCIETIXLX34X7FVK5B5WPZH22HXV342/>.
> +
>  if PYTHON
>  
>  config PYTHON_NCURSES
> -- 
> 2.20.1
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2020-05-07  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 13:08 [ptxdist] [PATCH] " Roland Hieber
2019-10-25  7:28 ` Michael Olbrich
2020-04-29 16:23   ` [ptxdist] [PATCH v2] " Roland Hieber
2020-05-07  8:12     ` Michael Olbrich [this message]

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=20200507081212.GB1153@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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