Tom Fleet

I may me missing something but could you not just do something similar to nox's own `ci.yml` i.e: ```python # noxfile.py @nox.session(python=ALL_SUPPORTED_VERSIONS_HERE) def test(session: nox.Session) -> None: """ Runs all...

> @FollowTheProcess : sure we can do as you suggest, but it only works for a single session, non-parametrized, and you have to put all versions in the yaml. >...

Just some further thoughts on this (mainly brainstorming). There are two major sticking points that I can see: - Synchronising or gathering up the console output from concurrently executing sessions...

I'd be cautious of this personally. I can't recall an exact working (or rather breaking) example right now but I've created several environments in the past where the lack of...

> Besides with pip the latest pip implementing PEP-660 there's no more case when pip would use the provisioned wheels/setuptools. Huh, cool! I wasn't aware of this, thanks!

This would be a cool feature! It's not nox but I've used [doit](https://pydoit.org) for these types of things before and it works quite well. My only complaint is that it's...

Great idea! 🎉

Continuing my walk through some older issues. It sounds to me like there are two things being conflated here: 1) The ability to do something like `session.background` for launching a...

Just a thought on the API here, I think a context manager would be the cleanest way of doing this IMO, taking inspiration from how `concurrent.futures` handles things Something like:...

I like it, although personally I've never had any problems with tools picking up the python I want to use (other than on windows) but I am quite obsessive and...