diff options
author | Daniel Schadt <kingdread@gmx.de> | 2022-12-09 21:07:20 +0100 |
---|---|---|
committer | Daniel Schadt <kingdread@gmx.de> | 2022-12-09 21:15:05 +0100 |
commit | 5ab50deb4c784e8c07e8600a4a95aafb3b146f75 (patch) | |
tree | 7edb911822b9cc6bb544291a0503819e4a0ddab4 /tests/integration/test_browse.py | |
parent | f919c404ba11886395c4669734cf11a68af4d904 (diff) | |
download | fietsboek-5ab50deb4c784e8c07e8600a4a95aafb3b146f75.tar.gz fietsboek-5ab50deb4c784e8c07e8600a4a95aafb3b146f75.tar.bz2 fietsboek-5ab50deb4c784e8c07e8600a4a95aafb3b146f75.zip |
fix tox and poetry interaction
The Poetry FAQ[1] gives some options on how tox and poetry can be used
together, since both of them want to do the virtual env managing. Since
we mostly want to use tox as a venv manager and to easily run multiple
linters, and we want to have poetry do the dependency management, the
method of explicitely using `poetry install` seems to be the most
reasonable. This means we don't have to generate a requirements.txt file
or make duplicated listings of our dependencies in tox.ini.
[1]: https://python-poetry.org/docs/master/faq/#is-tox-supported
Diffstat (limited to 'tests/integration/test_browse.py')
0 files changed, 0 insertions, 0 deletions