From: "Michal Suchánek" <msuchanek@suse.de>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: Sphinx parallel build error: UnicodeEncodeError: 'latin-1' codec can't encode characters in position 18-20: ordinal not in range(256)
Date: Wed, 12 May 2021 09:01:57 +0200 [thread overview]
Message-ID: <20210512070157.GQ12700@kitsune.suse.cz> (raw)
In-Reply-To: <20210512082238.682f6aea@coco.lan>
On Wed, May 12, 2021 at 08:22:38AM +0200, Mauro Carvalho Chehab wrote:
> Hi Michal,
>
> Em Thu, 6 May 2021 19:48:49 +0200
> Michal Suchánek <msuchanek@suse.de> escreveu:
>
> > [ 127s] + :
> > [ 127s] + locale
> > [ 128s] LANG=en_US
> > [ 128s] LC_CTYPE="en_US"
> > [ 128s] LC_NUMERIC="en_US"
> > [ 128s] LC_TIME="en_US"
> > [ 128s] LC_COLLATE="en_US"
> > [ 128s] LC_MONETARY="en_US"
> > [ 128s] LC_MESSAGES="en_US"
> > [ 128s] LC_PAPER="en_US"
> > [ 128s] LC_NAME="en_US"
> > [ 128s] LC_ADDRESS="en_US"
> > [ 128s] LC_TELEPHONE="en_US"
> > [ 128s] LC_MEASUREMENT="en_US"
> > [ 128s] LC_IDENTIFICATION="en_US"
> > [ 128s] LC_ALL=
> > [ 128s] + echo LC_ALL=
> > [ 128s] LC_ALL=
> > [ 128s] + echo LANG=en_US
> > [ 128s] LANG=en_US
>
> Where those the locale settings that you used when the build
> failed?
>
> I tried to reproduce the bug here with, disabling the parallel run (as
> it masks the real error) with both:
>
> $ for i in LANG LC_ALL LC_ADDRESS LC_IDENTIFICATION LC_MEASUREMENT LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME; do echo $i=en_US; done
> $ make cleandocs && make SPHINXOPTS=-j1 htmldocs
>
> (this one caused lots of warnings on Debian, due to the
> settings at /etc/locale.gen)
>
> and:
>
> $ for i in LANG LC_ALL LC_ADDRESS LC_IDENTIFICATION LC_MEASUREMENT LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME; do echo $i=en_US.ISO-8859-1; done
> $ make cleandocs && make SPHINXOPTS=-j1 htmldocs
>
> Without any success.
>
> Could you please provide more details about the build VM and the git
> changeset that caused the issue?
It depends on what character set your en_US locale implements.
~> cat test.py
print("↑ᛏ个")
~> locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
~> python3 test.py
↑ᛏ个
~> LANG=en_US python3 test.py
Traceback (most recent call last):
File "test.py", line 1, in <module>
print("\u2191\u16cf\u4e2a\uf8f9")
UnicodeEncodeError: 'latin-1' codec can't encode characters in position 0-3: ordinal not in range(256)
~> LANG=C python3 test.py
↑ᛏ个
You can easily test if your python version can print UTF-8 in a specific
locale, and if necessary define an ISO-8859-1 locale for testing.
On some systems the situation is reversed - C locale is ASCII only, and
en_US is UTF-8, and it is possible that some systems don't ship an 8bit
locale at all.
Thanks
Michal
next prev parent reply other threads:[~2021-05-12 7:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 10:39 Sphinx parallel build error: UnicodeEncodeError: 'latin-1' codec can't encode characters in position 18-20: ordinal not in range(256) Michal Suchánek
2021-05-06 11:20 ` Mauro Carvalho Chehab
2021-05-06 13:32 ` Michal Suchánek
2021-05-06 14:24 ` Mauro Carvalho Chehab
2021-05-06 14:35 ` Michal Suchánek
2021-05-06 15:57 ` Markus Heiser
2021-05-06 16:46 ` Mauro Carvalho Chehab
2021-05-06 17:04 ` Markus Heiser
2021-05-06 17:27 ` Mauro Carvalho Chehab
2021-05-06 17:53 ` Markus Heiser
2021-05-06 18:06 ` Michal Suchánek
2021-05-07 8:52 ` Mauro Carvalho Chehab
2021-05-06 17:57 ` Randy Dunlap
2021-05-06 18:08 ` Matthew Wilcox
2021-05-06 21:21 ` Randy Dunlap
2021-05-07 6:39 ` Mauro Carvalho Chehab
2021-05-07 6:49 ` Randy Dunlap
2021-05-07 8:04 ` Mauro Carvalho Chehab
2021-05-07 8:35 ` Michal Suchánek
2021-05-07 8:56 ` Markus Heiser
2021-05-07 9:14 ` Mauro Carvalho Chehab
2021-05-07 9:51 ` Markus Heiser
2021-05-07 10:29 ` Michal Suchánek
2021-05-07 9:02 ` Mauro Carvalho Chehab
2021-05-08 9:22 ` Mauro Carvalho Chehab
2021-05-08 10:41 ` Michal Suchánek
2021-05-08 14:41 ` Mauro Carvalho Chehab
2021-05-08 15:55 ` Randy Dunlap
2021-05-08 17:09 ` Michal Suchánek
2021-05-08 17:46 ` Randy Dunlap
2021-05-10 6:22 ` Mauro Carvalho Chehab
2021-05-10 8:17 ` Mauro Carvalho Chehab
2021-05-06 17:48 ` Michal Suchánek
2021-05-06 17:59 ` Markus Heiser
2021-05-06 18:16 ` Michal Suchánek
2021-05-12 6:22 ` Mauro Carvalho Chehab
2021-05-12 7:01 ` Michal Suchánek [this message]
2021-05-12 7:18 ` Markus Heiser
2021-05-12 7:37 ` Markus Heiser
2021-05-12 7:59 ` Mauro Carvalho Chehab
2021-05-17 13:10 ` Michal Suchánek
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=20210512070157.GQ12700@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).