Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Adding poetry-release to poetry 1.6.1 breaks poetry. #6

Open
jflipts opened this issue Aug 30, 2023 · 1 comment
Open

Adding poetry-release to poetry 1.6.1 breaks poetry. #6

jflipts opened this issue Aug 30, 2023 · 1 comment

Comments

@jflipts
Copy link

jflipts commented Aug 30, 2023

When I add poetry-release to poetry 1.6.1 with poetry self add poetry-release (^0.3.1) this works but running any poetry command after that results in No module named 'poetry.core.semver'.

Before adding poetry-release this is the output of poetry env info

Virtualenv
Python:         3.10.9
Implementation: CPython
Path:           NA
Executable:     NA

System
Platform:   linux
OS:         posix
Python:     3.10.9
Path:       /home/jflipts/miniconda3
Executable: /home/jflipts/miniconda3/bin/python3.10

When I uninstall poetry and install poetry 1.5.1 and add poetry-release 0.3.1 everything works back as expected.

@pcrumley
Copy link

pcrumley commented Sep 7, 2023

Yeah the issue is that poetry-core deprecated that code: https://github.com/python-poetry/poetry-core/releases/tag/1.7.0 , it should be using the replacement code at: poetry.core.constraints.version. I'd love to know if the maintainer of this lib has plans to update the poetry release to support the new location for the semver code, or if they would be willing to review PRs that could fix this issue.

Thanks

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants