Closed MarshalX closed 11 months ago
I see there's an issue for this in the poeblix repository: https://github.com/spoorn/poeblix/issues/18
and the most confusing thing is that when i try to install your plugin it installs poeblix...
I've seen this kind of behavior before when Poetry's internal pyproject.toml/poetry.lock gets into a weird state, which makes Poetry keep reinstalling plugins that you installed before. I'm not sure where it's located on Mac, but it's in %APPDATA%/pypoetry
on Windows. You could delete those files and reinstall the plugins you want.
what do i miss? who depends on incombustible poeblix?
poetry-dynamic-versioning doesn't depend on it. If you've tried using poeblix before, then I think it's just stuck in Poetry's internal pyproject.toml.
Thank you! Yeah, I tried to use it before. I'll check where this file could be located
macOS path: ~/Library/Application Support/pypoetry
poetry self remove poeblix
Hi, perhaps I'm missing something... (something with my local env) Because you fixed compatibility in v1.0.1 (2023-08-21) (No module named 'poetry.core.semver') but I still can't use your awesome plugin with Poetry 1.6.x.
Here is what i get:
as you can see the problem in
poeblix
which doesn't support Poetry > 1.5and the most confusing thing is that when i try to install your plugin it installs
poeblix
...what do i miss? who depends on incombustible poeblix?
UPD.
after
pip uninstall poeblix
it looks like the problem was fixed... i didn't get it