On Fri, Dec 11, 2020 at 8:02 AM Jonathan Corbet <corbet@xxxxxxx> wrote: > > On Thu, 10 Dec 2020 12:39:42 +0900 > JaeSang Yoo <js.yoo.5b@xxxxxxxxx> 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. > Is this meaning that some people are using older Sphinx? Then, there's no chance to leave from Python2. By the way, the previous linked commit ID is tagged as v2.4.4 which is selected in requirements.txt > > 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. Sorry for my poor English writings. I thought most users are using virtualenv. As you know that virtualenv will help using the specific version of Python libraries and the Python interpreter's version. I'll try to describe what I tried to say. 1. The Sphinx check script recommends using virtualenv for preparing Sphinx document generation environment. 2. By the virtualenv, we can isolate the Python libraries and the interpreter's version. (for the Sphinx documentation build) 3. When all the people are using the virtualenv, It will install Sphinx v2.4.4, which doesn't support Python2. 4. The Sphinx installation will fail for Python2 users. And it could lead to "no need to consider Python2 compatibility" But as you told me above, Step 3 seems false. Still, we need to consider Python2. Thanks, JaeSang
