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
>> the package, e.g:
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 automate
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
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 -0700
Subject: Use lo
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 advices for intersp
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
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 In
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:
> dh_
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 Sp
9 matches
Mail list logo
