Right now, when I start a new project, I can choose a python version. Say I choose python ^3.12. Oh no! I just realized that triton and pytorch don't yet use python 3.12! No problem, I'll just downgrade my python version in my poetry pyproject.toml file. If I do that, then I get this error:

Current Python version (3.12) is not allowed by the project (3.11.5).

This is nonsense. Just downgrade the python version, treat it like any other library. I can solve the problem by deleting the directory and restarting the entire project, but that's just awful UX.

Poetry creates a virtual environment for use when it is first run, and then that python version appears to be locked for all time and I'm having a hell of a time changing it. When people on my team are off by third digit version numbers (3.11.5 vs 3.11.6), well, that means that each of us have created incompatible python versions and we can't run each other's code.

Please, please, please, please, just allow poetry to treat python like any other library, like it does when the project is first created.