John Luscombe

This is what I do: ``` /AppData/Roaming/pypoetry/venv/Scripts/pip.exe install ``` Which succeeds, but: ``` poetry show ``` Result: ``` Package not found ```

Yes, good point. I do that, and: ``` Error: poetry.lock not found. Run `poetry lock` to create it. ``` So I run `poetry self lock` with success. However: ``` >...

> > Also worth noting is using the workaround approach, the custom commands show up in poetry list, however using Poetry's internal environment, it does not. > Not sure what...

> Ah, `show` is based on the lock file and not solely iterating over the environment -- it will indeed not be great for this use case. Good old `pip...

So, I guess that goes back to my original problem, how is someone expected to create and test plugins before publishing them?

That makes sense, but plugins do not appear to work when installed with Poetry's `pip`. And as it is right now `poetry self` cannot install plugins from non-PyPi sources, so...

Are you referring to this? ``` [tool.poetry.plugins."poetry.plugin"] demo = "poetry_demo_plugin.plugin:MyPlugin" ``` Is that just supposed to be defined in the plugin repo? I install it from within that repo (using...

I see, looks like I had two `poetry` installations that were competing with each other, one installed with the script and one installed via the system `pip`. The poetry `pip`...