All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain <ju.o@free.fr>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	Marcin Niestroj <m.niestroj@grinn-global.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/python-referencing: select package/python-typing-extensions
Date: Wed, 26 Feb 2025 22:58:44 +0100	[thread overview]
Message-ID: <9644da8a1ec5586cc0a9a8812352ecdc@free.fr> (raw)
In-Reply-To: <20250225220100.3076207-1-fiona.klute@gmx.de>

On 25/02/2025 23:00, Fiona Klute via buildroot wrote:
> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
> 
> The referencing module requires either Python >= 3.13 or
> typing-extensions, otherwise import fails. The dependency was added
> with 0.36.0, and to Buildroot with commit 94cf596d76
> "package/python-referencing: bump to version 0.36.1".
> 
> Initial change requiring Python >= 3.13:
> https://github.com/python-jsonschema/referencing/commit/5ea5a1539378f80caa9d6969849ee61667cb7252
> Fix to support earlier Python versions with typing-extensions:
> https://github.com/python-jsonschema/referencing/commit/71cbd0008d02c5a320176dab2da046aa0d20a6e9
> 
> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>

Series applied to master, thanks.

> This patch should naturally be dropped if Python is updated to 3.13, 
> the
> second one is relevant either way.

We will revert it after Python will be bumped to 3.13.

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2025-02-26 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250225220100.3076207-1-fiona.klute@gmx.de>
2025-02-25 22:01 ` [Buildroot] [PATCH 2/2] package/python-typing-extensions: update homepage link in help Fiona Klute via buildroot
2025-03-14 10:23   ` Peter Korsgaard
2025-02-26 21:58 ` Julien Olivain [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=9644da8a1ec5586cc0a9a8812352ecdc@free.fr \
    --to=ju.o@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=james.hilliard1@gmail.com \
    --cc=m.niestroj@grinn-global.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.