Supported python versions, pre-commit tests, sphinx

Vincent Ladeuil v.ladeuil+lp at free.fr
Wed Jun 2 07:20:16 BST 2010


>>>>> Robert Collins <robertc at robertcollins.net> writes:

    > Currently we support python2.4 and up, and build optional docs via
    > sphinx. sphinx seems to be nicer than what we were using before, and
    > Ian wants to delete the old cruft:)

    > However our pre-commit testing environment currently runs 'hardy', and
    > that does not have python-sphinx available.

    > We have a few of [easyish] options.
    >  - don't make this change
    >  - stop testing that the docs build
    >  - backport sphinx to hardy
    >  - change the test environment to run 'lucid'

How about producing a distinct tarball for the docs (or several) ? This
will free us from requiring a specific OS version to run it and we can
set up a job on babune so that we check for regressions.

Failing that backporting sphinx may be the best route but I'm a bit
concerned that we will open a can of worms there.

    > These have different tradeoffs.
    > If we stop testing that docs build, we pretty much guarantee that
    > errors will creep in.

True, on the other hand, failure to just produce the docs reveals only
minor problems (so to speak), most of the errors are caught by humans
reading the docs and reporting bugs.

        Vincent



More information about the bazaar mailing list