poetry env info --path unable to locate the virtual env directory in some situations

[jamesrobson-secondmind]

I was experimenting with a tool called sphinx-polyversion which creates a temporary directory, runs a poetry install then uses poetry env info --path to identify the directory the virtual env was created in. This works fine running locally, however when run in Jenkins env info --path doesn't produce any output or error message. This seems to be because poetry decides there isn't a virtual env.

If I connect to a worker then polyversion fails although just running env info --path in a checkout of my repo works. Presumably this is caused by something in the environment on the worker. Does anyone have any insight into what the cause could be?

[jamesrobson-secondmind]

Part of the cause seems to be having a different versions of python used by the project and poetry. For some reason in the temp dir poetry would look for a virtual env created for its own python rather than the project python.
It's not clear why this is happening, but as a simple work around I can use pipx to install poetry with the same version of poetry used by the project and then everything works