Closed jason-neal closed 6 years ago
Hi,
Thanks for reporting this unpleasant behavior. I can reproduce the error in a fresh virtualenv with both Python 2 and 3.
A simple question first: Does it (betasig) work for you after an install without --with-ext?
Although I have not yet understood the details of the error, it is certainly related to the presence of some FORTRAN code in the package, which is, however, only relevant for some transit light-curve models. The --with-ext option triggers (or tries to trigger as it appears now) the compilation of this code (first via f2py). Without --with-ext, setup.py serves you a message (looking suspiciously like a complaint, I admit). This should, however, not break the install of the remaining package. I did not want to make --with-ext the default pure and simple, because I expected more trouble than good from it.
At any rate, I will try to figure out the origin of the error.
Cheers, Stefan
A simple question first: Does it (betasig) work for you after an install without --with-ext?
Yes. Now that I have tried it. I had gotten a little confused by the lack of install information between the different stages.
running build
running build_py
running install_lib
...
So I thought it had not been installed at all, and never tried to run it.
I think it may have also been a problem (in a different repo) with having version 0.11 pip installed and then trying to python setup.py install version 0.13beta. (not yet realizing that version 12 was available from pip)
Great it did not break because of this.
The reason for the ".pyf" error appears to be that neither setup from distutils nor setuptools supports compilation of fortran code. Only the extended version from numpy does this. I adapted setup.py to reflect this. Hope this is resolved.
Stefan
I cloned the most recent version of master (to try out beta sigma) and have issues installing it into a fresh conda environment. I ran
pip install -r requirements.txt
and then the commands down below.Trying to install without
--with-ext
complained about the extensions not being build and then using--with-ext
gives a different error about unknown file type.pyf
files.Have you seen this before/have a solution for this. Am I missing some sort of compiler?