Recent searches
Search options
I’ve been often asked why I’m using Nox for running my #Python #test suites lately. I’ve been evading the question because I can’t explain it without contrasting it with Tox, a project very dear to my heart.
I’ve finally given in: Why I Like Nox: https://hynek.me/articles/why-i-like-nox/
I've updated the article based on @ubernostrum observation in https://lobste.rs/s/983b6p/why_i_like_nox#c_zrnxmp
The fact that Python versions are a first-class selector in Nox can simplify your CI config. I've also added some Bash to handle the edge case of pre-release version specifiers. 
Check it out: https://hynek.me/articles/why-i-like-nox/#bonus-tip-python-versions-as-first-class-selectors
@adamchainz@fosstodon.org@hynek @ubernostrum FYI tox 4 added the -f flag to select envs by factors, e.g. you can run all Python 3.11 envs with:
tox -f py311
In my GitHub Actions setups I run one per Python env with:
tox run -f py$(echo ${{ matrix.python-version }} | tr -d .)
@adamchainz @ubernostrum right I remember playing with it, but there was something weird and I didn’t write it down 
@adamchainz @hynek I've not really messed around with tox 4 -- my attempts to get it working on GH Actions led to re-re-exploring, and ultimately adopting, nox.