Fix #15 - installing from pip
and easy_install
(Take 2)
#21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
build_ext
task is called beforebuild_py
togenerate SWIG .py files before the Python copy step happens and we
miss packaging and installing the generated files.
test_install
for testing multiple build andinstall methods on the active Python installation.
This is much cleaner; not sure why it didn't occur to me last night. I think this should work with any install method entry point into setuptools because it's explicitly hooking into
build_py
, which should always be called.The new Makefile target isn't the cleanest thing ever. I just wanted an automated way to test the whole clean installation loop into my local Python install.