Call f2py via subprocess.call, install of directly calling main function #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Using Win 7 64bit I also had the same problem. DavidPowell's modification works for me. |
|
Seems fair enough! thanks |
mgaitan
added a commit
that referenced
this pull request
Jan 10, 2015
Call f2py via subprocess.call, install of directly calling main function
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I found that the problems with failing to find the fortran compiler under windows can be resolved by calling the f2py script, rather than directly calling the main() function. I'm not sure why this should fix the problem, perhaps it has something to do with all the environment variables needed to get fortran compilers running under windows.
Fixes #7.