python-poetry / python-poetry/install.python-poetry.org
install.python-poetry.org with constraints.txt
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 255
- Forks
- 65
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 1
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Feature Request
Currently when running poetry-install.py for a specific version the dependencies of that specific poetry version are resolved at install time and may include recently published versions.
For example, poetry==1.1.11 required cryptography>=2.0
This has been incrementing to pull a newer and newer version of cryptography which ultimately broke a CI docker build I run when the newest version started requiring a rust compiler.
It would be great if we could deterministically install poetry - even if that required the 1-time generation of a poetry-install lock file.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading poetry-install.py and the constraints.txt context in the issue, then trace how dependencies are resolved for a requested Poetry version. Define how a generated lock or constraints file would be used; done means installing a specific Poetry version produces deterministic dependency versions without requiring newly published incompatible packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100