Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.datemas.de!news.albasani.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Thomas Goirand Newsgroups: linux.debian.maint.python Subject: Re: sphinx-build vs. Python 3 Date: Mon, 20 Aug 2018 12:40:01 +0200 Message-ID: References: X-Original-To: debian-python X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Aug 20 10:37:02 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: Debian User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/16238 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/e0989250-c651-57cf-a0bf-d320e0cf1a7b@debian.org Approved: robomod@news.nic.it Lines: 35 Sender: robomod@news.nic.it X-Original-Date: Mon, 20 Aug 2018 12:36:43 +0200 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:10817 On 08/20/2018 09:50 AM, Ondrej Novy wrote: > Hi, >=20 > I have question about sphinx-build and our effort to move to Python 3. >=20 > sphinx-build is currently Python 2 or Python 3 according to > python-sphinx / python3-sphinx package installed (with python3 as > default if both are installed by alternative priority).=C2=A0 >=20 > According > to:=C2=A0https://wiki.debian.org/Python/LibraryStyleGuide#Sphinx_docume= ntation we > should use "python3 -m sphinx" if we want to build docs using Python 3, > because if you run sphinx-build, you can't be sure which version of > Sphinx is run and if you need some Sphinx extension, which we typically > installs only Python 2 or Python 3 version of it. >=20 > And my question is: > * should we use "python3 -m sphinx" instead of "sphinx-build" everywher= e > where python3-sphinx is in B-D (mass-commit?) > OR > * should we change sphinx-build to be Python3 only? (and broke current > packages build with Python2 Sphinx) >=20 > Thanks for your opinions. If you do the later, then anyway, you'll have to do the former if you need backports. This bite me a few times with OpenStack already. So, no mater what the faith of the sphinx-build command, it's always best to use python3 -m sphinx, IMO. Cheers, Thomas Goirand (zigo)