Closed yarden closed 9 years ago
My thinking is that --with-cython
can be for building from the git repository with python setup.py
and not pip, while the distribution on pypi won't need it because it will have the .cpp
files included. I don't think supporting pip install .
is absolutely necessary if we have those two clear paths working.
However, you're right that a fully automatic version would be a better solution. So should we just call cython if the .cpp files aren't present? How would developers signal that they want to force cython to be called (even if the .cpp files are present)?
The latest at https://github.com/mattjj/pyhsmm/pull/39 should now do this. It doesn't rely on cython if it's not present (i.e. if you're in a source distribution), it error checks to see that the .cpp files are actually there, and it works with pip install .
so it can support automation.
Moving over to #39 (when I get a chance to respond!).
I just tried your new
setup.py
and it does not compile for me:I can try to fix it while integrating travis. Relying on custom flags like
--with-cython
I think is a bad idea, because package mangers won't know about these. It also seems like the flag is unnecessary.python setup.py build_ext
orpython setup.py sdist
can figure out if Cython needs to be called and if so run it.