You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like numpy has made some changes to f2py in v1.10.x that are breaking the python-fsps build. They are reverting some of those changes, it is unclear at this point which change in particular has broken the build.
For now the solution is to use numpy 1.9.3 and below. I'll try and see if the latest f2py changes on the numpy development version have fixed the problem, or if we need to open an issue with numpy
The text was updated successfully, but these errors were encountered:
Finally got a spare machine to test on. Using the latest numpy development version (v1.11.0.dev0+765422c, numpy/numpy@765422c) installed from source with python 2.7.10 I was able to successfully build and install python-fsps (v0.2.1, a571e44).
Basically everything except numpy v1.10.x should work. It looks like they introduced a bug in 1.10 while trying to make the f2py documents adhere to style guidelines. As soon as v1.11 is released I will update the requirements.
just to note, the fixes in numpy 1.11 have apparently been backported to 1.10.4 (and possibly earlier versions), such that python-fsps now successfully compiles with macports 1.10.4. @dr-guangtou, hope this helps
It looks like numpy has made some changes to f2py in v1.10.x that are breaking the python-fsps build. They are reverting some of those changes, it is unclear at this point which change in particular has broken the build.
For now the solution is to use numpy 1.9.3 and below. I'll try and see if the latest f2py changes on the numpy development version have fixed the problem, or if we need to open an issue with numpy
The text was updated successfully, but these errors were encountered: