Re: [PATCH] python: python3-idna: fix non-existent Unicode license

Konrad Weihmann <kweihmann@...>

I think the Unicode should be clear, as the tool (in)directly uses downloads from unicode, but kindly ignores the licensing part of that operation.

Looking into the history of that lib I found, which explains the Python-2.0 part. Not sure, but I think that one can be dropped now.

Maybe someone should raise a ticket upstream to tell them, that even though they convert the upstream unicode data, they still have to apply the unicode terms and conditions

On 02.12.21 17:37, Khem Raj wrote:
On Wed, Dec 1, 2021 at 8:14 AM Quentin Schulz
<quentin.schulz@...> wrote:

In addition to not being an SPDX license, Unicode license also isn't
available in any of the LICENSE_PATH available in openembedded, meaning
the following warning is printed:

python3-idna: No generic license file exists for: Unicode in any provider [license-exists]

Unfortunately the license is not really explicit in the project. After
looking at the code, it seems that this license gets pulled by
idna/ and idna/ which are auto-generated by
tools/idna-data which downloads data from{version}/ucd/ and which are covered by as mentioned in

Comparing to Unicode-DFS-2016
resulted in a match so let's point to that SPDX license instead.

Cc: Quentin Schulz <foss+yocto@...>
Signed-off-by: Quentin Schulz <quentin.schulz@...>
meta/recipes-devtools/python/ | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/python/ b/meta/recipes-devtools/python/
index a0e6b79a56..f3c53a8717 100644
--- a/meta/recipes-devtools/python/
+++ b/meta/recipes-devtools/python/
@@ -1,6 +1,11 @@
SUMMARY = "Internationalised Domain Names in Applications"
-LICENSE = "BSD-3-Clause & Python-2.0 & Unicode"
+# Note: Unicode license is pulled in by idna/ and idna/
+# files auto-generated by tools/idna-data which downloads data from
+#{version}/ucd/ and
+# which are covered by as mentioned by
+LICENSE = "BSD-3-Clause & Python-2.0 & Unicode-DFS-2016"
LIC_FILES_CHKSUM = "file://;md5=239668a7c6066d9e0c5382e9c8c6c0e1"
I looked at
and they seem to indicate that it is BSD-3-Clause so where do the
other licenses come from ?

SRC_URI[sha256sum] = "9d643ff0a55b762d5cdb124b8eaa99c66322e2157b69160bc32796e824360e6d"

Join { to automatically receive all group messages.