python-poetry / python-poetry/install.python-poetry.org
Support more ways of specifying the installation version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 255
- Forks
- 65
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 1
Description
Currently, the way script handles versioning is simply by passing the version over to pip as poetry=={version}. This is fine, however it would be nice if we could set the version to something like ^1.3.0, or similar.
This probably shouldn't be too hard to handle, as there's already a regex checking for semver compatibility, and these are just some set of additional characters that could optionally be there. If this specifier isn't there, the script can just use the current approach of ==.
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
Read the installer script's existing semver validation regex and the code that passes the version to pip. Check how the current poetry=={version} argument is assembled, then verify that supported specifiers such as ^1.3.0 preserve their intended form while plain versions keep the current behavior. Done means the accepted version forms are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100