Note - this is the first time I'm using pipenv, so I just set up the project with pipenv install --dev which functionaly works, but caused the lockfile to be updated. That seems as correct behaviour to me, but depending on which exact minor version of Python you're using, this may lead to ever-changing lock files.
I'm also not sure if the package dependencies should be specified in the Pipfile if they're already present in setup.py - as pip install -e . already takes care of pulling in the dependencies for local development.
Fixes #41
Note - this is the first time I'm using pipenv, so I just set up the project with
pipenv install --dev
which functionaly works, but caused the lockfile to be updated. That seems as correct behaviour to me, but depending on which exact minor version of Python you're using, this may lead to ever-changing lock files.I'm also not sure if the package dependencies should be specified in the
Pipfile
if they're already present insetup.py
- aspip install -e .
already takes care of pulling in the dependencies for local development.