Do we really need tox?

[ulgens]

While working with #1792, I realized that tox setup has some issues, and I tried to understand what is going on. Apparently, there is only one version of Python and Django that we test againist, and the tox config doesn't look like it does more than chaining tests and linting. tox is not needed for Django tests and the rest can be handled by pre-commit.

[adamzap]

I think it'd be great if we could remove it.

I wonder if tox is useful for the pattern seen in these two commits where a new Python version is added to test against along side the old one before the old one is removed:

• 164c840
• 70895c1

I'm looking forward to hear what others think!

[ulgens]

@adamzap For those cases, wouldn't it be enough to test in on a new branch?

[adamzap]

It should be. I personally think that would be ideal, but I don't know the current process.

[pauloxnet]

I also don't think we need tox here.
Maybe we can open a draft PR to see all the required changes to get rid of it.