Making sure pip-grep runs in the project directory #26
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.
Running
pip-grep
outside the project directory causes problems for projects with direct dependency references in the same file system. E.g., arequirements.txt
file like this:Is currently failing because the
numpy-scipy
script invokespip-grep
inside the.heroku
directory, instead of inside the project directory itself.This PR changes the behavior so
pip-grep
is called from the project directory. Hopefully this shouldn't change the behavior in any other way.