Poetry
Replies: 2 comments
-
|
I also tried using pip to install. I was hoping to get some insight into what the version resolution was doing. The errors are interesting but still confusing.
Gave me the error: I am very confused here. Yes mycoolplugin 1.0.3 depends on poetry 2.1.3 and 1.0.2 does depend on poetry 2.1.1. The thing is are in fact running in a venv with Poetry 2.1.3 so shouldn't that resolve the conflict? There is no conflict this command is running under poetry 2.1.3 so it already knows it should be using version 1.0.3. What am I miss reading about this message? Full command and response: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I tried specifying the version I want too. First showing the poetry version for the venv: This command gave me an error But I am running in poetry 2.1.3 and version 1.0.3 of my plugin is for poetry 2.1.3. Again am I miss reading this error message? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I got my first poetry plugin nearly working. Version 1.0.2 was installed in our team Pypi repo and Poetry was able to install it into my test client project and I could use its commands. Unfortunately some of the code was didn't execute because it was built with 3.13.5 and the client project's poery was using python 3.10.
No problem I just moved everybody to 3.13.5 and build a 1.0.3 version of my plugin.
Now when I execute
poetry installafter creating the venv I get:Sadly
mycoolpluginis not included in the environment. The requirement seems to be just ignored.My
myclienttoolpyproject.tomlfile looks like this:My
mycoolpluginpyproject.tomlfile looks like this:Previously when I used Poetry 2.1.1 and
myclienttoolrequiredmycoolpugin1.0.2 the plugin was installed into the venv this way.So, first question shouldn't this work? I am following the instructions from here: https://python-poetry.org/docs/plugins/#project-plugins
I posted about this on stackoverflow and someone suggested using a different method to install my plug in. This method is also documented here: https://python-poetry.org/docs/plugins/#the-self-add-command
poetry self add https://artifactory.company.com/team-pypi/mycoolplugin/1.0.3/mycoolplugin-1.0.3-py3-none-any.whlI figured it couldn't hurt and maybe I'd get more info. However now things fail because pip is trying to downgrade
pbs-installerin my venv.The TLDR is
Why is it trying to downgrade pbs-installer? The mentions of dependencies (other than the one above that says 2025.7.12 depends on 2025.7.12) say that anything from 2025.01.01 to 2026.0.0 are acceptable.
More importantly why is this even happening when all I want is mycoolplugin installed.
Full command and output:
Beta Was this translation helpful? Give feedback.
All reactions