linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: JaeSang Yoo <js.yoo.5b@gmail.com>
Cc: mchehab+huawei@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.org, markus.heiser@darmarit.de
Subject: Re: [PATCH] docs: update requirements to install six module
Date: Thu, 10 Dec 2020 16:02:05 -0700	[thread overview]
Message-ID: <20201210160205.56bb9060@lwn.net> (raw)
In-Reply-To: <CAHdLnN2b5viH--nuqEERePQd47inF9cYqFLaThd3VVAvz5u76g@mail.gmail.com>

On Thu, 10 Dec 2020 12:39:42 +0900
JaeSang Yoo <js.yoo.5b@gmail.com> wrote:

> While I was surveying the Sphinx library, it requires Python version
> 3.5 as a minimum.
> You can figure it out in the setup.py of Sphinx library source:
> https://github.com/sphinx-doc/sphinx/blob/72ad5f2a/setup.py#L13-L15

That, of course, applies to current Sphinx releases. We have people
building with older releases, though, which still work with Python 2.

> I assume this would be a certain reason to leave Python 2 behind. The
> Sphinx check script recommends using virtualenv. How do you think
> about leaving Python 2 compatibility issue in this documentation
> script range?

I'm sorry, I don't quite understand your question.

Thanks,

jon

  reply	other threads:[~2020-12-10 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08  1:46 [PATCH] docs: update requirements to install six module JaeSang Yoo
2020-12-08  6:28 ` Mauro Carvalho Chehab
2020-12-10  0:29 ` Jonathan Corbet
2020-12-10  3:39   ` JaeSang Yoo
2020-12-10 23:02     ` Jonathan Corbet [this message]
2020-12-11  1:15       ` JaeSang Yoo
2020-12-11 20:55         ` 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=20201210160205.56bb9060@lwn.net \
    --to=corbet@lwn.net \
    --cc=js.yoo.5b@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab+huawei@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).