[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d17b90zb.fsf@intel.com>
Date: Thu, 31 Aug 2017 19:05:28 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Jonathan Corbet <corbet@....net>,
Mauro Carvalho Chehab <mchehab@...pensource.com>
Cc: "linux-doc\@vger.kernel.org" <linux-doc@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-media <linux-media@...r.kernel.org>
Subject: Re: [PATCH 1/2] docs: kernel-doc comments are ASCII
On Thu, 31 Aug 2017, Randy Dunlap <rdunlap@...radead.org> wrote:
> On 08/31/17 07:17, Jonathan Corbet wrote:
>> On Thu, 31 Aug 2017 10:56:26 -0300
>> Mauro Carvalho Chehab <mchehab@...pensource.com> wrote:
>>
>>> It should have something to do with python version and/or to some
>>> locale info at the system, as neither I or Jon can reproduce it.
>>
>> I can't reproduce it here, but I have certainly seen situations where
>> Python 2 wants to run with the ascii codec by default.
>>
>> Note that the exception happens in our Sphinx extension, not in Sphinx
>> itself. We've had other non-ascii text in our docs, so I think Sphinx is
>> doing the right thing. The problem is with our own code. If I could
>> reproduce it, it shouldn't be too hard to track down - take out that
>> massive "except anything" block and see where it explodes.
>>
>> Randy, which distribution are you running, and are you using their version
>> of Sphinx?
>
> opensuse LEAP 42.2
> Yes, their sphinx 1.3.1.
What's your LANG setting? I think that's what it boils down to, and
trying to work around non-UTF-8 LANG in both python 2 and 3 compatible
ways.
The odd thing is that I can reproduce the issue using a small python
snippet, but not through Sphinx.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
Powered by blists - more mailing lists