Wow, I'm actually surprised at how unconvinced I am. Moving from a declarative config syntax to arbitrary Python is rarely a good idea, and "the point of this is to run commands" feels pretty flat to me - after all, the "point" of setup.py was to run commands, but we all know the problems that caused.
Very good write-up. It has certainly made Nox pique my interest.<p>Sadly, I don't think I'll use it. It's hard to justify jumping into a project using Tox and replacing it without reason.<p>However, if at any time something breaks with Tox, or I need to so something that's feeling super hacking, I'll definitely consider it.
I did a video <a href="https://www.youtube.com/watch?v=cAkMVIBTFbQ">https://www.youtube.com/watch?v=cAkMVIBTFbQ</a> converting, as a proof of concept, an OpenStack project to use nox. I liked it, and anytime I went "oh no, it doesn't do X" I found it does, and I learned how.<p>It's always hard to evaluate a young project vs an older one; but nox seems good and I would likely use it for a greenfield project in the future.