-
I did ask this earlier on Stackoverflow but no one has commented or answered and I have more information now (maybe).
I have written an application plugin for poetry. That project has a section in the pyproject.toml file like this:
It builds and creates the expected wheel. I can run and test its commands in that project and during tests run by pytest. In the project that I want to use the plugin the pyproject.toml file contains:
I have now published the plugin to the company pypi site. However poetry install still does this:
I read https://github.com/orgs/python-poetry/discussions/9469 which shows that the resolver is super sensitive to the version of python in ways I also would not have expected. It seems the error message misses what is really happening and sure enough my plugin project has:
While my project that would like to use the plugin had
so I changed it to
So that it matched but that gave the exact same error. Additional notes:
[[tool.poetry.source]] What is going on? Why doesn't poetry find the plugin when the versions match? Is it really complaining about version mismatch or is it really unable to find it? What can I do to fix this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Oh this is interesting - now I'm more confused. I ran `poetry install -vv' and see some things I expect:
That is the expected vm that I setup and created. But What is it using python 3.10 for? That is not the version of python I have in my venv. It is the version of python that is installed on our nfs under poetry 2.1.1 but I specifically created a venv that includes the versions of poetry and python that we want to use on this project.
|
Beta Was this translation helpful? Give feedback.
-
Just had a suggestion (from AI) that I try
Sounds like I should be looking at my pypi repo setup... |
Beta Was this translation helpful? Give feedback.
-
Solved. I added the needed pypi repo. We have a company clone of pypi with approved libraries but also my team has its own where we place things we produce. That's where my plugin resides so my project needed to reference that repo too. Fair enough. |
Beta Was this translation helpful? Give feedback.
Solved. I added the needed pypi repo. We have a company clone of pypi with approved libraries but also my team has its own where we place things we produce. That's where my plugin resides so my project needed to reference that repo too. Fair enough.