From: Thomas Gleixner <tglx@linutronix.de> To: Nishanth Menon <nm@ti.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org, Rahul T R <r-ravikumar@ti.com>, Nishanth Menon <nm@ti.com> Subject: Re: [PATCH] scripts/spdxcheck.py: Lets strictly read license files in utf-8 Date: Wed, 07 Jul 2021 11:00:31 +0200 [thread overview] Message-ID: <87h7h6qz0w.ffs@nanos.tec.linutronix.de> (raw) In-Reply-To: <20210703012128.27946-1-nm@ti.com> Nishanth, On Fri, Jul 02 2021 at 20:21, Nishanth Menon wrote: > Commit bc41a7f36469 ("LICENSES: Add the CC-BY-4.0 license") > unfortunately introduced LICENSES/dual/CC-BY-4.0 in UTF-8 Unicode text Sigh. Why are people adding such things w/o running this script in the first place. > While python will barf at it with: > > FAIL: 'ascii' codec can't decode byte 0xe2 in position 2109: ordinal not in range(128) > Traceback (most recent call last): > File "scripts/spdxcheck.py", line 244, in <module> > spdx = read_spdxdata(repo) > File "scripts/spdxcheck.py", line 47, in read_spdxdata > for l in open(el.path).readlines(): > File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode > return codecs.ascii_decode(input, self.errors)[0] > UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 2109: ordinal not in range(128) > > While it is indeed debatable if 'Licensor.' used in the license file > needs unicode quotes, instead, let us force spdxcheck to read utf-8 > instead. s/let us// Ditto for the $subject. See Documentation/process/ for further enlightment. > Reported-by: Rahul T R <r-ravikumar@ti.com> > Signed-off-by: Nishanth Menon <nm@ti.com> With that fixed: Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2021-07-07 9:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-03 1:21 Nishanth Menon 2021-07-07 9:00 ` Thomas Gleixner [this message] 2021-07-07 16:53 ` Jonathan Corbet
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=87h7h6qz0w.ffs@nanos.tec.linutronix.de \ --to=tglx@linutronix.de \ --cc=gregkh@linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-spdx@vger.kernel.org \ --cc=nm@ti.com \ --cc=r-ravikumar@ti.com \ --subject='Re: [PATCH] scripts/spdxcheck.py: Lets strictly read license files in utf-8' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).