Earlier quoted context omitted.
To me, that’d be a UX nightmare. Even if I tried to, I’m not going to memorize which of my 20 checked-out Python projects are requiring which Python invocation. IMHO it’s absolutely the toolchain’s job to manage that for me. I’d never adopt a toolchain that wouldn’t.
You do know that python is backwards compatible right? You can just use 3.11 with everything.
If my project is a library that needs to support e.g. 3.8 through 3.11, then I’m not going to use 3.11 for my development environment.
The same goes if my project depends on a library or framework that doesn’t support 3.11.