elasticsearch-docker is developed under a test-driven workflow, so please refrain from submitting patches without test coverage. If you are not familiar with testing in Python, please raise an issue instead.
To ensure that we are always running the pytest (and other dependencies) that are installed in the virtualenv for this project, without requiring the user to "activate" the virtualenv.
Why is this hardcoded?
Does this PR include tests? No
elasticsearch-docker
is developed under a test-driven workflow, so please refrain from submitting patches without test coverage. If you are not familiar with testing in Python, please raise an issue instead.