Repository navigation
Fix doc building to use astropy source - #187
Conversation
|
Very welcome change. For me, |
|
Awesome, thanks for fixing this. I'm seeing the same docs/docs behavior, but otherwise seems good. We've put a lot of work, I think, into developing workarounds to a lot of the annoyances with Python software builds--it seems almost worth pulling out a lot of Astropy's package framework as a drop-in template to use for arbitrary Python-based projects (we've already done that to an extent with the affiliated package template, thought that's still tied to Astropy). But that's another project for another time :) |
|
I agree. The infrastructure for this project is really good! |
|
The errant 'docs' directory was because I was changing into the docs directory in the subprocess to get it to put the generated docs in the right place... but that meant the directory names from the @iguananaut - Yeah, maybe we should make our own packaging/build tools from scratch and call it |
|
This works for me! The docs appear in the right place. |
|
Alright, looks like its all building as expected. Merging! |
Fix doc building to use astropy source
Fix doc building to use astropy source
(ports astropy#187 to master) Conflicts: astropy_helpers/test_helpers.py
Fixing this was more subtle than I realized, but this PR now finally makes the sphinx build operate consistently. Now,
python setup.py build_sphinxalways uses the version of astropy in the build directory, whilemake htmlin thedocsdirectory will use the installed version.As part of this, a critical bug is fixed that in the past meant you had to have the C extensions installed via
python setup.py developorpython setup.py build_ext --inplaceto get the docs to build. That is no longer the case.This closes #134 .