Do we need tox? #29

Open
opened 2021-05-15 16:02:55 +02:00 by Jef Roosens · 0 comments
Owner

Tox is cool 'n' all, but considering our CI is dockerized it's really just a hassle more than anything. We could just run make test in each Python version container and be done with it.

It also creates concurrency issues that could be solved by just creating a venv for each version.

Tox is cool 'n' all, but considering our CI is dockerized it's really just a hassle more than anything. We could just run `make test` in each Python version container and be done with it. It also creates concurrency issues that could be solved by just creating a venv for each version.
Jef Roosens added this to the 1.0.0 milestone 2021-05-15 16:02:55 +02:00
Jef Roosens added the
enhancement
label 2021-05-15 16:02:55 +02:00
Jef Roosens self-assigned this 2021-05-15 16:02:55 +02:00
Jef Roosens added this to the 1.0.0 project 2021-05-15 16:02:55 +02:00
Jef Roosens added
Brainstorm
and removed
enhancement
labels 2021-05-15 16:05:14 +02:00
This repository is archived. You cannot comment on issues.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Chewing_Bever/backup-tool#29
No description provided.