From: Quentin Schulz <quentin.schulz@cherry.de>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 2/2] tools: Update the license specifiers
Date: Tue, 29 Apr 2025 15:28:35 +0200 [thread overview]
Message-ID: <016f585f-fd30-4604-8676-c7cabd9e40a1@cherry.de> (raw)
In-Reply-To: <20250429131515.244061-2-sjg@chromium.org>
Hi Simon,
On 4/29/25 3:15 PM, Simon Glass wrote:
> Recent versions of Python complain about the license being in the
I believe this isn't related to Python but rather setuptools.
setuptools 77.0.3 and later support PEP-639 which recommends to ditch
the License :: classifier for a license property.
The issue is that this license property also changed in PEP-639, with
something that isn't compatible with pre-PEP-639.
Therefore we need to bump the minimum requirement for the setuptools
dependency in the various pyproject.toml to 77.0.3 or later.
I'm also wondering if we don't need to add a license-files property
(also PEP-639) to comply with the GPL-2.0-or-later which requires to
provide a copy of the license.
Cheers,
Quentin
next prev parent reply other threads:[~2025-04-29 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 13:15 [PATCH 1/2] tools/make_pip.sh: Use debian packages instead of pip Simon Glass
2025-04-29 13:15 ` [PATCH 2/2] tools: Update the license specifiers Simon Glass
2025-04-29 13:28 ` Quentin Schulz [this message]
2025-04-29 13:52 ` Tom Rini
2025-04-29 14:04 ` Quentin Schulz
2025-04-29 14:27 ` Tom Rini
2025-04-29 13:43 ` [PATCH 1/2] tools/make_pip.sh: Use debian packages instead of pip Quentin Schulz
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=016f585f-fd30-4604-8676-c7cabd9e40a1@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=alpernebiyasak@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 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.