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
When setting up a test development environment, the included Makefile has a target env that should create a virtual environment and install the development dependencies. However, the make env command fails because requirements-dev.txt is not present in the repository.
Steps to Reproduce
git clone the repository
Change to the repository directory
run make env
Expected behavior: The environment is installed and ready for development and testing
Actual behavior: The virtualenv is created, but pip fails to install dependencies with error Could not open requirements file: [Errno 2] No such file or directory: 'requirements-dev.txt'
Reproduces how often: all the time
Versions
Not applicable
Additional Information
This is on branch master, but it may be present in other branches.
The text was updated successfully, but these errors were encountered:
Historically Makefile was used as a set of shortcuts, make test or make env are some of them.
As this project aims to support multiple python environments, it uses tox as the main environment manager and this is preferred way compared to make env. To avoid confusions, I've removed make env and make test commands. tox -e <ENV> should be used instead.
Description
When setting up a test development environment, the included Makefile has a target
env
that should create a virtual environment and install the development dependencies. However, themake env
command fails becauserequirements-dev.txt
is not present in the repository.Steps to Reproduce
git clone
the repositorymake env
Expected behavior: The environment is installed and ready for development and testing
Actual behavior: The virtualenv is created, but pip fails to install dependencies with error
Could not open requirements file: [Errno 2] No such file or directory: 'requirements-dev.txt'
Reproduces how often: all the time
Versions
Not applicable
Additional Information
This is on branch
master
, but it may be present in other branches.The text was updated successfully, but these errors were encountered: