
language: python

python:
  - "2.6"
  - "2.7"
  - "3.3"
  - "3.4"

before_install:
  - sudo apt-get update -qq
  - sudo apt-get install -y doxygen texlive-latex-base texlive-latex-extra texlive-fonts-recommended

install:
  - pip install -r requirements/production.txt
  - pip install .

env:
  - TRAVIS_CI=True

# Builds all examples & html documentation
#
# Provide definition for DOXYGEN variable to stop it trying
# to run `which doxygen`
script: make DOXYGEN=doxygen DEBUG=""



language: python

env:
  - SPHINX_VERSION=1.2.3 TRAVIS_CI=True
  - SPHINX_VERSION=1.3.1 TRAVIS_CI=True

python:
  - "2.6"
  - "2.7"
  - "3.3"
  - "3.4"

before_install:
  - sudo apt-get update -qq
  - sudo apt-get install -y doxygen texlive-latex-base texlive-latex-extra texlive-fonts-recommended

install:
  - pip install Sphinx==$SPHINX_VERSION
  - pip install .

# Builds all examples & html documentation
#
# Provide definition for DOXYGEN variable to stop it trying
# to run `which doxygen`
script: make DOXYGEN=doxygen DEBUG=""


Test with two versions of Sphinx
Test with two versions of Sphinx

I do not consider compatibility with old versions to be essential but I
believe we are so it would be good to test it to make sure that we don't
accidentally drift away.

We can then consciously remove older versions as we choose. Two reasons
for not overly valuing backwards compatibility are that Sphinx is a
documentation generator and therefore not a core code path for most
projects and so they can afford to update more easily, and also we use
internal Sphinx APIs which are more likely to change and so be hard to
stay compatible with multiple versions.

Here we use the Travis environment functionality to test two versions of
Sphinx as recommended here:

    http://docs.travis-ci.com/user/languages/python/#Testing-Against-Multiple-Versions-of-Dependencies-(e.g.-Django-or-Flask)
