pyenv only manages python versions, while poetry manages dependencies and virtual environments. They are complimentary, but do not overlap.

To add to this, with poetry, you basically do `poetry env use python3.12` to create a python virtualenv on python3.12 (you can use whatever python version pyenv supports, doesn't even have to be CPython).

The generated virtual env name is a little wonky. I'm not sure exactly what the scheme is, but it's basically `$(package)-$(some sort of hash?)-$(pyversion)`. I can't speak for all tools, but at least VS Code detects the poetry env and suggests it (and indicates it as a Poetry env) when you go to configure the project interpreter.

You can use the poetry config to enable poetry putting the virtualenv into the project folder itself, which allows most IDEs to discover it.