On Sat, Dec 20, 2008 at 7:43 AM, Stéfan van der Walt <[email protected]> wrote: > 2008/12/20 Ondrej Certik <[email protected]>: >> So we thought with Stefan that maybe a simpler solution is just to fix >> the ./setup sdist (or how you create the tarball in numpy) to include >> documentation and be done with it. > > I think releases should either include the Sphinx documentation or, > alternatively, we should provide a separate tar-ball for the docs > along with every release.
How difficult would it be to generate the doc ? I have not followed in detail what happened recently on that front. Is sphinx + sphinx ext the only necessary additional tools ? What I did for audiolab recently was to use paver to generate the source distribution for releases: the release sdist generates the usual sdist (which is kept the same as before - e.g. no need for tools to build the doc), as well as the doc (html + pdf), and put everything together. Paver is a mere convenience, and this could be done with simple scripts, of course, David _______________________________________________ Numpy-discussion mailing list [email protected] http://projects.scipy.org/mailman/listinfo/numpy-discussion
