Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Communicate a projects used poetry version in a team #3469

Closed
1 task done
tmbo opened this issue Dec 9, 2020 · 3 comments
Closed
1 task done

Communicate a projects used poetry version in a team #3469

tmbo opened this issue Dec 9, 2020 · 3 comments
Labels
area/docs Documentation issues/improvements

Comments

@tmbo
Copy link

tmbo commented Dec 9, 2020

  • I have searched the issues of this repo and believe that this is not a duplicate.

Issue

Since the lockfile format changed in 1.1.x an update of poetry requires all developers working on the project to upgrade their poetry version.

Previously, the pyproject.toml contained the version of the recommended poetry version to use for a project, e.g.

[build-system]
requires = [ "poetry>=1.0.4",]
build-backend = "poetry.masonry.api"

This got replaced though, with a reference to the poetry-core builder (which uses independent versioning scheme). Therefore, it is unclear what the recommended way is to communicate the used poetry version. Do you have any recommendations?

@tmbo tmbo added area/docs Documentation issues/improvements status/triage This issue needs to be triaged labels Dec 9, 2020
@sinoroc
Copy link

sinoroc commented Dec 9, 2020

Duplicate of #3316 ?

Also I do not think it should have been filed with the Documentation tag.

@tmbo
Copy link
Author

tmbo commented Dec 9, 2020

yes you are right. thanks for the pointer - the combination "poetry version" is just very hard to search for 😂

@tmbo tmbo closed this as completed Dec 9, 2020
@abn abn removed the status/triage This issue needs to be triaged label Mar 3, 2022
Copy link

github-actions bot commented Mar 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/docs Documentation issues/improvements
Projects
None yet
Development

No branches or pull requests

3 participants