Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From: Ghislain Vaillant <ghisvail@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: building manpages via setup.py
Date: Wed, 02 Aug 2017 10:20:02 +0200
Message-ID: <u9X2O-7mD-21@gated-at.bofh.it>
References: <u9GEH-5cQ-19@gated-at.bofh.it> <u9Hr4-5Jr-23@gated-at.bofh.it> <u9W6J-6Ni-3@gated-at.bofh.it> <u9Wgq-6Qo-9@gated-at.bofh.it> <u9WzL-6Xn-9@gated-at.bofh.it> <u9WzL-6Xn-7@gated-at.bofh.it> <u9WzM-6Xn-25@gated-at.bofh.it> <u9X2O-7mD-23@gated-at.bofh.it>
Old-Return-Path: <ghisvail@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Approved: robomod@news.nic.it
Lines: 19
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:9670

On 02/08/17 09:03, PICCA Frederic-Emmanuel wrote:
>> Perhaps the LibraryStyleGuide should be updated to reflect on this
>> change? I believe we are still advising explicit http_proxy /
>> https_proxy exports prior to running sphinx-build.
> 
> And running sphinx-build does not work expecially if there is extensions in the documentation.
> sphinx-build should be run via pybuild in order to know about the build_dir.
> 
> right ?

At the end of the day, it is just a matter of providing an appropriate 
PYTHONPATH, regardless of whether pybuild is used or not.

The default is $(CURDIR) for the vast majority of packages. But, it may 
also be something else if extension packages are involved, or if the 
package directory is under a different folder than the root directory, 
such as src/.

Ghis