I would prefer to stick with tox and remove nox instead.

@kurtmckee To be honest, it is not a big difference. And it seems our nice friends at pypa like it, so we are not adopting something that is unmaintained.

I much more strongly disagree with this now that I've attempted to run the tests on Windows.

nox is finding PyPy 3.9 and believes that it's CPython 3.9. It's not able to find 4 of my installed CPython versions.

This appears to be happening because PyPy 3.9 and CPython 3.11 are the only ones on my PATH (and my virtual environment was created using Python 3.11). The nox documentation says that it finds Python versions on Windows using the py launcher, which I don't have installed.

nox -- on Windows, anyway -- appears to be an inferior product to tox in this regard, and I would like to revert this change and use tox instead.

@ericof Please let me know if reverting this change and standardizing on tox will be acceptable.

@kurtmckee open a PR reverting all nox changes

Not sure what happened with this as the code review failed to check about other tox lefovers,

https://github.com/search?q=repo%3Acookiecutter%2Fcookiecutter%20tox&type=code reports lots of files referring to tox.

@ssbarnea I'm pretty sure that I reverted the changes a long time ago, as discussed above.

#2157 discarded the tox configuration in the last 24 hours, so the old discussion here has become very irrelevant to the current state of the repo.