Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/python: clarify that this refers to the deprecated 2.7 series
Date: Mon, 8 Feb 2021 18:46:45 +0100	[thread overview]
Message-ID: <20210208184645.2beb3433@gmx.net> (raw)
In-Reply-To: <20210208132412.29013-1-peter@korsgaard.com>

Hello Peter,

On Mon,  8 Feb 2021 14:24:11 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:

> Python 2.7 is EOL, so people should use the python3 package instead if
> possible.  Make it a bit more obvious that 'python' is not the right package
> to use by explicitly mentioning that this if about python 2.7 and that it is

s/this if about/this is about/?

Reviewed-by: Peter Seiderer <ps.report@gmx.net>

Regards,
Peter

> deprecated.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
>  package/python/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/python/Config.in b/package/python/Config.in
> index bded00c9e8..ab6950cae8 100644
> --- a/package/python/Config.in
> +++ b/package/python/Config.in
> @@ -3,7 +3,7 @@ comment "python needs a toolchain w/ wchar, threads, dynamic library"
>  	depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
>
>  config BR2_PACKAGE_PYTHON
> -	bool "python"
> +	bool "python2.7 (deprecated)"
>  	depends on BR2_USE_WCHAR
>  	# uses fork()
>  	depends on BR2_USE_MMU

  reply	other threads:[~2021-02-08 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 13:24 [Buildroot] [PATCH] package/python: clarify that this refers to the deprecated 2.7 series Peter Korsgaard
2021-02-08 17:46 ` Peter Seiderer [this message]
2021-02-08 21:11 ` 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=20210208184645.2beb3433@gmx.net \
    --to=ps.report@gmx.net \
    --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