How to install a plugin but manage (e.g. pin) plugin dependencies

[hozn]

I'm trying to install poetry-grpc-plugin on my M1 Mac. Dealing with the grpcio dependency on the M1 Mac is fraught with drama. Basically you have to use third-party-distributed pre-compiled binaries right now.

For my regular project dependencies, Poetry lets me do this crazy dance like this:

[tool.poetry.dependencies]
Python = "^3.10"
grpcio = [
    {markers="sys_platform == 'darwin' and platform_machine=='arm64'", path='./vendored/grpcio-1.50.0-cp310-cp310-macosx_11_0_arm64.whl'},
    {version="^1.50.0", markers="sys_platform != 'darwin' and platform_machine!='arm64'", source="pypi"}
]
grpcio-tools = [
    {markers="sys_platform == 'darwin' and platform_machine=='arm64'", path='./vendored/grpcio_tools-1.50.0-cp310-cp310-macosx_11_0_arm64.whl'},
    {version="^1.50.0", markers="sys_platform != 'darwin' and platform_machine!='arm64'", source="pypi"}
]

... However ... if I install the grpc plugin, even using a virtualenv that has already been initialized by poetry (poetry install --with dev), it looks like it decides to grab its own version of grpcio and then of course fails to build on my mac (for various compile errors that are the topic of numerous grpcio bugs out there).

I'm doing:

poetry self add poetry-grpc-plugin

As hinted above, I've tried this both from my global poetry install as well as a poetry that has been installed into my local virtualenv. (I've configured poetry to use in-directory venvs for this.)

Is there an easy way to install this plugin but force it to use my already-installed dependencies? The 1.50.0 version that I've installed locally meets the plugin's requirements from pyproject.toml; however, it does not meet the pinned versions in poetry.lock.

(Is poetry.lock even used when installing a plugin in this manner?)

Thanks in advance!

[neersighted]

You should not mix Poetry (and its plugins) with the environment your project is installed into. Poetry will happily update the versions to satisfy your project's needs, which will include breaking itself. If you need to add additional packages to Poetry's environment, poetry self add is the best method.

As for poetry-grpc-plugin itself, you will have to reach out to the plugin author for support.

[hozn]

Ok, it makes sense that mixing the virtualenv is not the right answer.

I'm deducing from this answer that the poetry.lock file for the plugin is indeed being respected when installing into Poetry's environment and there's no way to provide a constraint.txt file or mechanism to change these at install (poetry self add ...) time? Pinning deps using plugin lock file seems surprising, as I'd expect that this would make it more likely for plugins to conflict with each other.

My workaround was to track down deps that matched the pinned versions for the plugin, manually install the dependencies from local vendored directory using pip, and then install the plugin.