TST: Fixed f2py test for win32 virtualenv#7116
Merged
charris merged 1 commit intonumpy:masterfrom Jan 25, 2016
gfyoung:f2py_patch
Merged
TST: Fixed f2py test for win32 virtualenv#7116charris merged 1 commit intonumpy:masterfrom gfyoung:f2py_patch
charris merged 1 commit intonumpy:masterfrom
gfyoung:f2py_patch
Conversation
Fixed test_scripts.test_f2py test so that it can pass correctly on win32 virtualenvs, in which the Python executable and the f2py.py file are both in the Scripts directory.
Member
|
LGTM, although I can't test it. |
Contributor
Author
|
I ran it locally on my machine, and it passes just fine. |
charris
added a commit
that referenced
this pull request
Jan 25, 2016
TST: Fixed f2py test for win32 virtualenv
Member
|
Thanks @gfyoung . |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixed
test_scripts.test_f2pytest so that it can pass correctly on win32 virtualenvs, in which the Python executable and thef2py.pyfile are both in theScriptsdirectory.