From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 610BD6DE1272 for ; Sun, 24 Dec 2017 05:44:10 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLqe8buRowyp for ; Sun, 24 Dec 2017 05:44:09 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 85E176DE1209 for ; Sun, 24 Dec 2017 05:44:09 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1eT6ZU-0004ZO-Mm for notmuch@notmuchmail.org; Sun, 24 Dec 2017 08:44:08 -0500 Received: (nullmailer pid 4541 invoked by uid 1000); Sun, 24 Dec 2017 13:44:07 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: Re: [RFC] test: build python docs In-Reply-To: <20171224131452.811-1-david@tethera.net> References: <20171224131452.811-1-david@tethera.net> Date: Sun, 24 Dec 2017 09:44:07 -0400 Message-ID: <87mv2844wo.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2017 13:44:10 -0000 David Bremner writes: > The idea is to consider any warning from sphinx-build as a test > failure. This requires the -W option, which we probably don't want for > builds. > --- > > I'm not sure the best way to do this. An alternative approach would be > to build the python docs during the main build (much as we currently > build the ruby bindings). I suspect we'd want some way to disable the > "-W" option to sphinx-build in that case, so that python doc failures > don't break the entire build. On the other hand, for distros breaking > the test suite is pretty much equivalent to breaking the build. In the > proposed patch the test could be disabled by dropping sphinx-build > from the test env (which makes the man pages go away), or by patching > the single test out. Sure enough, no sooner do I send this and fix the warning about get_config_list, I get others that I don't see an obvious fix for: /home/bremner/software/upstream/notmuch/bindings/python/docs/source/status_and_errors.rst:17: WARNING: error while formatting arguments for notmuch.STATUS: 'Status' object has no attribute '__bases__' /home/bremner/software/upstream/notmuch/bindings/python/docs/source/threads.rst:14: WARNING: don't know which module to import for autodocumenting u'__str__' (try placing a "module" or "currentmodule" directive in the document, or giving an explicit module name)