Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-30 Thread Nikolaus Rath
On Sep 30 2016, Florent Rougon wrote: >>> Instead of attempting circumvention of the effect of using intersphinx, >>> it's best to simply *DISABLE* intersphinx in the conf.py of the >>> documentation. >> >> Even better than disabling intersphinx is to ship the required data in

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-30 Thread Thomas Goirand
On 09/30/2016 08:13 AM, Florent Rougon wrote: > Or use the following alternative, which lets the user browse the > documentation offline. I found it very nice to do that indeed, but probably too much time consuming for the package maintainer. It'd be nice if we found a way to make it more

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-30 Thread Dmitry Shachnev
Hi Thomas, On Thu, Sep 29, 2016 at 11:22:08PM +0200, Thomas Goirand wrote: > On 09/27/2016 10:48 AM, Ben Finney wrote: > > Our wiki page on Library Style Guide advises the Debian packaging > > override the Python import path: > > > > If you need to build the Sphinx documentation (usually from

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-30 Thread Florent Rougon
Or use the following alternative, which lets the user browse the documentation offline. $ cat debian/patches/use-local-python3-doc-for-cross-references >From f519a948173bfd4e9700a4ebc60bc54bf3455018 Mon Sep 17 00:00:00 2001 From: Florent Rougon Date: Thu, 8 Oct 2015 13:28:35

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-29 Thread Nikolaus Rath
On Sep 29 2016, Thomas Goirand wrote: > On 09/27/2016 10:48 AM, Ben Finney wrote: >> https://wiki.debian.org/Python/LibraryStyleGuide#Sphinx_documentation > > I just had a quick look to that page, not only it advises to override > the wrong dh sequence, but also it gives stupid

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-29 Thread Barry Warsaw
On Sep 29, 2016, at 11:30 PM, Thomas Goirand wrote: >I just had a quick look to that page, not only it advises to override >the wrong dh sequence, but also it gives stupid advices for intersphinx: ObDIY: "It's a wiki". :) Cheers, -Barry

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-29 Thread Thomas Goirand
On 09/27/2016 10:48 AM, Ben Finney wrote: > https://wiki.debian.org/Python/LibraryStyleGuide#Sphinx_documentation I just had a quick look to that page, not only it advises to override the wrong dh sequence, but also it gives stupid advices for intersphinx: "sphinx-build might try to access the

Re: Upstream build system, Sphinx autodoc, Python import path

2016-09-29 Thread Thomas Goirand
On 09/27/2016 10:48 AM, Ben Finney wrote: > Our wiki page on Library Style Guide advises the Debian packaging > override the Python import path: > > If you need to build the Sphinx documentation (usually from .rst or > .md files), add: > > override_dh_auto_build: >

Upstream build system, Sphinx autodoc, Python import path

2016-09-27 Thread Ben Finney
Howdy all, What advice can we give to upstream for their build system, so that in a Debian build environment the Sphinx ‘autodoc’ can import upstream's code modules? Our wiki page on Library Style Guide advises the Debian packaging override the Python import path: If you need to build the