Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Dmitry Shachnev Newsgroups: linux.debian.maint.python Subject: Re: [Python-modules-team] Bug#830186: sphinx: intersphinx mapping extension causes network access during package builds Date: Mon, 18 Jul 2016 10:30:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jul 18 08:26:11 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.467 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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-lf0-f68.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=20130820; h=x-gm-message-state:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=edh1/icIYgdym0LG6HQu+oGfBa2tMCpOXylIpCNDlww=; b=dPlhdcts5ybJuF0lkFN5d6QWjrWL5AP8vtCNFH1HZp6rIZ8/2A818QBeU6nd9T6mQC pW5QRNCqwWyTk6BY9PSislzFM3ccrq4WYohVg3PXXCle2wK+9wqMO0LA7+Fh0eXbvFF4 mOiQ+zGhE0LW7bfDdwz0p/0bG+jKv0+fu0uOQBFJwNr6kjWVhqYb6fBbX7Ova1sEysLb MpM3Inc5fj0uZIaYDMSpC7LctluP+mXxwwiGDp/FzowQ3Yy82KICFAqA7SEsUNixu9MO Ki13qjoR5Hz7IaDKj+vzAbiBsxog+5nfNocE5bGl4l75NXomxtiA41LqjxYWZr58Yyfo rmKA== X-Gm-Message-State: ALyK8tId8RHQUnJDYo7OfScldiw+nKS9biqJQtY9iO0ceWLgB10Kd/Ulej59bB7S6CbVoQ== X-Received: by 10.25.146.85 with SMTP id u82mr13113113lfd.222.1468830355988; Mon, 18 Jul 2016 01:25:55 -0700 (PDT) User-Agent: K-9 Mail for Android MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-Mailing-List: archive/latest/14004 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/AB395B60-E942-4EF0-88D7-4F0B2C646263@debian.org Approved: robomod@news.nic.it Lines: 22 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Mon, 18 Jul 2016 10:25:48 +0200 X-Original-Message-ID: X-Original-References: <1467878033.2235446.659246769.7769F4C6@webmail.messagingengine.com> <20160707193017.GA9300@mitya57.me> <8737nitgw2.fsf@prune.linuxpenguins.xyz> <20160711180657.GB5782@mitya57.me> <87mvlnsvc2.fsf@prune.linuxpenguins.xyz> <20160711220117.GA21103@mitya57.me> <87vb05ox6q.fsf@prune.linuxpenguins.xyz> Xref: csiph.com linux.debian.maint.python:8666 Hi Brian, On July 17, 2016 3:44:29 AM GMT+02:00, Brian May wrote: > Dmitry Shachnev writes: > > > Setuptools provides a build_sphinx command out of the box. For > packages > > using distutils, there is a sphinx.setup_command module provided by > > Sphinx. > > > > Some upstreams call that command during build phase, though that’s > not > > common. > > Is there any reason that this isn't more common? Should I be doing > this > for my packages which I maintain upstream? If you are both the upstream and the packager, then adding a few lines in debian/rules to build the documentation is probably easier than hacking the build command in setup.py. -- Dmitry Shachnev