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 Sp

Re: Review/sponsorship of osmalchemy package

2016-09-27 Thread Thomas Goirand
On 09/12/2016 03:39 PM, Dominik George wrote: > Hi, > > I would like to ask for review and sponsorship of the osmalchemy package. > > It can be found in the usual place at: > git.debian.org:/git/python-modules/packages/osmalchemy.git > > The package can be build with gbp using pristine-tar. It a

[WAS: Re: Review/sponsorship of osmalchemy package] md , rst, txt, html, ...

2016-09-27 Thread Jerome BENOIT
Hello Forum, On 27/09/16 23:41, Thomas Goirand wrote: > debian/docs: > > * It looks like the README.rst could be transformed into .html using > sphinx. Could you do that? It'd look a lot nicer. Some software comes with a README.md, README.rst, ... which are the same version of a tex

Re: [WAS: Re: Review/sponsorship of osmalchemy package] md , rst, txt, html, ...

2016-09-27 Thread Guido van Steen
Hi Jerome, I may not fully understand the issue, but why not keep *.md, *.rst, *.pod, etc. the way they are? The main advantage of *.md, *.rst, *.pod, etc. is their readability. Their additional advantage is that they can easily be transferred into *.html or many other formats, if desired. A mis