Thanks guys for the hints. Yes indeed, I've checked the Sid within
Cowbuilder and the environment is set to "C". But here, several attempts
to change the build LC_LANG failed so far being effective for the Sphinx
build, and that error remains. I'll come back when I've got deeper into
that issue.
Greetings,
Daniel
On 24.07.2014 18:06, Etienne Millon wrote:
* Barry Warsaw <ba...@python.org> [140724 17:41]:
I don't remember the details, but I think there are some build
environments where the locale is not set correct (or not set?),
which can cause Python's default encodings to kick in and make
incorrect assumptions (albeit based on limited available
information). I think I've seen this with sbuilds occasionally.
The fix is usually to be explicit about the encoding or make sure
the locale is set to UTF-8. It'll also work differently depending
on whether you're using Python 2 or 3.
Sorry I'm a little fuzzy on the details - it's been a while.
Hopefully that gives enough of a clue to keep digging in the right
place.
I had the problem with a build environment which resets LC_ALL to C or
unsets it (can't remember if it's at the pbuilder or pybuild level).
To print a (unicode) string, python3 needs to know how to encode the
string and uses locale for that. In my case the following worked:
override_dh_auto_test:
LC_ALL=C.UTF-8 dh_auto_test
--
http://www.danielstender.com/blog/
PGP key: 2048R/E41BD2D0
C879 5E41 1ED7 EE80 0F2E 7D0C DBDD 4D96 E41B D2D0
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53d1707a.90...@danielstender.com
