≈
Fix setup to allow installing from PyPi
Another attempt at fixing the setuptools problem
Fix pip incantation
Fix typo
Try updating setuptools too
Try upgrading pip and setuptools after venv install
Rule out install_requires as the source of the problem
Try just requiring the ones that can be built from source
Use explicit install_requires and move version checks to after setup runs
Clean up installation for PyPI compatiblity
Dead end commit
Fix travis to match new installation procedure
Put build_versions check after install
Fix travis syntax
Switch to lower-case cython in version check
Another attempt
Another fix
Fix syntax error
Make header executable
Build inplace on py27
Fix finding of source code version in sphinx
Fix travis syntax
Import setuptools after install
Fix the version check in sphinx
Work around setuptools bug in 2.7
Fix handling of Cython requirement and update release notes
Switch to one Appveyor build and update build method
Add cython back to install_requires
Remove debug lines
Another try for appveyor install
Another attempt at setuptools and Appveyor
Do not let intermittent apt-get failures crash the build
Fix typo
Another appveyor attempt
More fixes for setuptools and Appveyor
Yet another setuptools/appveyor attempt
Put requirements.txt back in order
Fix typo
Fix readlines function call
Try not using a venv for python 2.7
Fix syntax
Try the provided venv for py27
Remove --user
Remove debug info
Another try for python27 fix
Try again
Do not use install_requires with numpy/scipy
Try just avoiding scipy
Try removing scipy (numpy was before)
Avoid both scipy and numpy
Fix qt install on 27
Fix qt install on 27 agin
Revert the scripts to their previous condition
Revert file permission changes
Undo changes to requirements.txt
Previously, apigen documented all but the bottom-most level of modules in the package tree. This caused problems when different subpackages had different depths. Instead, just document subpackages (ignore python files, whose public functions should already be loaded into the subpackage).
Documenting inherited methods and attributes can lead to overly verbose docs. For example, the `Image` class, which subclasses ndarray, and various viewer-related classes, which subclass PyQt and Matplotlib classes, have hundreds of irrelevant methods added to the API docs.
Either the role should be removed (as done here) or the inheritance-diagram extension needs to be added to the config file. Since skimage doesn't have a complicated class hierarchies, it's probably best to remove.
__import__ can get confused about which scikits path to import when multiple scikits are present on a system.
Note that `root_module` is no longer an attribute of `ApiDocWriter` (it wasn't being used anywhere), and it now points to "scikits.image" instead of "scikits".
Stefan van der Walt