Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #10829

Re: sphinx-build vs. Python 3

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Dmitry Shachnev <mitya57@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: sphinx-build vs. Python 3
Date Tue, 21 Aug 2018 15:10:02 +0200
Message-ID <wpeA2-2YE-1@gated-at.bofh.it> (permalink)
References <woNq9-3Oq-3@gated-at.bofh.it>
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Aug 21 13:03:42 2018
Old-Return-Path <mitya57@gmail.com>
X-Amavis-Spam-Status No, score=-11.498 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-lj1-f175.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ZQouHy+83VAO3Z4PNIsxgDPKMjB8rczc5eOumd4WU2U=; b=UB53U5r4xHZiuVUzRpQ08LsVFtv/gP+SWXhXijsde3kGseuP96qhfgUsvcEv+b0eqL BuMk8t29dFDRPXg/5/sKKd9N0GMUhyHByHbQiMLm8jevAzolvSMMbuSH1sua+zp0kg/E 5vmlNel5ONg1Eqep0P/gbObXrUJ8zdy7jAm37UXQrPudADaJn9AH0qxDIT3libciPKbZ qcRwdcSP02lKdCnmMrK0Y5EiUywlsYR3khtDhDXypviuegvYIYbjBDnazeh8FiEdiF0g 6GNMvYKbt/gNDZPesx61rR8h2iNJvvwPD7sO+vqXZaEW21tEYl0zX3aBSqZhS4OVfpLc 90fA==
X-Gm-Message-State AOUpUlGRv0u34IvmEetNKmTPFLWg6fykt9Ho0yviMTcsLz2UYjNWLe3e biqqVo9kX9gtDSt6wkMgT0nw+/az
X-Google-SMTP-Source AA+uWPxnVd2xYFYr3NClloWo234DJSqpCrzWfINIgzb0LaCYHTlVvdRtzMZHpqcfYJrnHVxh9b2duQ==
X-Received by 2002:a2e:504d:: with SMTP id v13-v6mr33244378ljd.84.1534856604181; Tue, 21 Aug 2018 06:03:24 -0700 (PDT)
MIME-Version 1.0
Content-Type multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw"
Content-Disposition inline
User-Agent Mutt/1.10.1 (2018-07-13)
X-Mailing-List <debian-python@lists.debian.org> archive/latest/16249
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20180821130320.GA19039@mitya57.me
Approved robomod@news.nic.it
Lines 77
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Tue, 21 Aug 2018 16:03:20 +0300
X-Original-Message-ID <20180821130320.GA19039@mitya57.me>
X-Original-References <CAOO6c=x1ct-idZy1S9WJM2wnT-FEeQewfEo8QAApCdX1+o4eXw@mail.gmail.com>
Xref csiph.com linux.debian.maint.python:10829

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi Ondřej!

On Mon, Aug 20, 2018 at 09:50:25AM +0200, Ondrej Novy wrote:
> Hi,
>
> I have question about sphinx-build and our effort to move to Python 3.
>
> 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).
>
> According to:
> https://wiki.debian.org/Python/LibraryStyleGuide#Sphinx_documentation 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.

That wiki page was written before I changed Sphinx scripts to use Python 3
by default. That happened only recently, the relevant upload reached
unstable on July 5th 2018.

If you depend on python3-sphinx (>= 1.7.5-4~) then most likely the scripts
will be using Python 3. The opposite will happen only if the user manually
updated the alternative, and this won’t be the case on a sane build
environment.

> And my question is:
> * should we use "python3 -m sphinx" instead of "sphinx-build" everywhere
> where python3-sphinx is in B-D (mass-commit?)

This won’t hurt, but as I said it won’t make any difference on the current
unstable. It will make difference only when building against an older version
of sphinx (e.g. backports) *and* with installed python-sphinx.

> * should we change sphinx-build to be Python3 only? (and broke current
> packages build with Python2 Sphinx)

I would like to do this in the future, but currently there will be too
many broken packages:

https://lintian.debian.org/tags/build-depends-on-python-sphinx-only.html
lists 386 packages.

--
Dmitry Shachnev

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

sphinx-build vs. Python 3 Ondrej Novy <novy@ondrej.org> - 2018-08-20 10:10 +0200
  Re: sphinx-build vs. Python 3 Thomas Goirand <zigo@debian.org> - 2018-08-20 12:40 +0200
    Re: sphinx-build vs. Python 3 Ondrej Novy <novy@ondrej.org> - 2018-08-21 10:50 +0200
      Re: sphinx-build vs. Python 3 Thomas Goirand <zigo@debian.org> - 2018-08-21 12:40 +0200
        Re: sphinx-build vs. Python 3 Ondrej Novy <novy@ondrej.org> - 2018-08-21 13:00 +0200
  Re: sphinx-build vs. Python 3 Dmitry Shachnev <mitya57@debian.org> - 2018-08-21 15:10 +0200
    Re: sphinx-build vs. Python 3 Mattia Rizzolo <mattia@debian.org> - 2018-08-21 22:30 +0200

csiph-web