From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH 1/2] docs: kernel-doc comments are ASCII
Date: Thu, 31 Aug 2017 08:47:10 -0700 [thread overview]
Message-ID: <f9e30c84-7ad7-39dd-a39f-f62581f0b893@infradead.org> (raw)
In-Reply-To: <20170831081721.38be05ef@lwn.net>
On 08/31/17 07:17, Jonathan Corbet wrote:
> On Thu, 31 Aug 2017 10:56:26 -0300
> Mauro Carvalho Chehab <mchehab@s-opensource.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.
--
~Randy
next prev parent reply other threads:[~2017-08-31 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 23:10 [PATCH 1/2] docs: kernel-doc comments are ASCII Randy Dunlap
2017-08-30 21:23 ` Jonathan Corbet
2017-08-30 22:02 ` Randy Dunlap
2017-08-30 22:15 ` Mauro Carvalho Chehab
2017-08-30 22:31 ` Jonathan Corbet
2017-08-30 23:01 ` Randy Dunlap
2017-08-30 23:04 ` Randy Dunlap
2017-08-30 23:15 ` Randy Dunlap
2017-08-31 9:49 ` Mauro Carvalho Chehab
2017-08-31 13:26 ` Jani Nikula
2017-08-31 13:56 ` Mauro Carvalho Chehab
2017-08-31 14:17 ` Jonathan Corbet
2017-08-31 15:47 ` Randy Dunlap [this message]
2017-08-31 16:05 ` Jani Nikula
2017-08-31 16:24 ` Randy Dunlap
2017-08-31 16:36 ` Jani Nikula
2017-08-31 17:34 ` Randy Dunlap
2017-08-31 17:54 ` Randy Dunlap
2017-08-31 17:55 ` Jani Nikula
2017-08-31 18:08 ` Randy Dunlap
2017-08-31 15:44 ` Randy Dunlap
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=f9e30c84-7ad7-39dd-a39f-f62581f0b893@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
/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).