First `poetry install` does not include dynamic version about poetry-dynamic-versioning HOT 4 CLOSED

Hi! If you don't have the plugin installed globally and you're just relying on the entry in tool.poetry.dependencies, then the plugin won't become available until Poetry has installed it in the virtual environment. It's not given any kind of preferential treatment to be installed before everything else, so it has to wait like any other dependency, and by then it's too late to activate during the first run.

I did confirm that the plugin activates during an initial poetry install if the plugin is installed globally.

Also, you would probably want to put the plugin in dev-dependencies instead.

from poetry-dynamic-versioning.

Hi, what does installed globally mean? Poetry installed via get-poetry.py is installed into its own environment which isn't really accessible for the user. A package such as this installed globally via pip will not be accessible by poetry.

from poetry-dynamic-versioning.

Nevermind, seems like this is a hole in the the current way of doing things and also the new plugin system: python-poetry/poetry#693 (comment)

from poetry-dynamic-versioning.

When you install Poetry with get-poetry.py, the Poetry launcher script basically adds its vendored dependencies (along with the Poetry module itself) onto the PYTHONPATH and then launches Python as normal, so it's not completely isolated from your global Python libraries. If you install the plugin with pip install poetry-dynamic-versioning, it can indeed work with Poetry regardless of which way Poetry was installed. The plugin is regularly tested with both Poetry installation methods as part of the GitHub workflow.

from poetry-dynamic-versioning.