IssueRaiser

Suggestion: new command to bump versions of dependencies in `pyproject.toml`

<!-- Hi there! Thank you for wanting to make Poetry better. Before you submit this; let's make sure of a few things. Please make sure the following boxes are ticked if they are correct. If not, please try and fulfill these first. --> <!-- Checked checkbox should look like this: [x] --> - [x] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. ## Issue <!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ --> It would be awesome if Poetry had a command (let's call it `upgrade`) that bumped the version constraints of dependencies in `pyproject.toml` (as opposed to `update`, which afaict updates the lock file to the newest version _within_ the constraint specified in `pyproject.toml`). Some examples for how this command could behave: - `poetry upgrade django`: Upgrade Django to the newest version that still works with other dependencies; equivalent to `poetry remove django; poetry add django`. - `poetry upgrade django djangorestframework`: As above, but with more than one package at a time. - `poetry upgrade django=^2.1`: Set the version of `django` to `^2.1`, equivalent to `poetry remove django; poetry add django=^2.1`. - `poetry upgrade`: Upgrade every dependency to the newest possible version. Equivalent to deleting the entire `[tool.poetry.dependencies]` section of `pyproject.toml` and running `poetry add` with a list of the names (but not versions) of every package

Posted by daisylb on Oct 2, 2018, 5:26 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

github (Software)

Suggestion: new command to bump versions of dependencies in `pyproject.toml`

daisylbOct 2, 2018, 5:26 AM

<!-- Hi there! Thank you for wanting to make Poetry better. Before you submit this; let's make sure of a few things. Please make sure the following boxes are ticked if they are correct. If not, please try and fulfill these first. --> <!-- Checked checkbox should look like this: [x] --> - [x] I have searched the [issues](https://github.com/sdispater/poetry/issues) of this repo and believe that this is not a duplicate. ## Issue <!-- Now feel free to write your idea for improvement. Thanks again 🙌 ❤️ --> It would be awesome if Poetry had a command (let's call it `upgrade`) that bumped the version constraints of dependencies in `pyproject.toml` (as opposed to `update`, which afaict updates the lock file to the newest version _within_ the constraint specified in `pyproject.toml`). Some examples for how this command could behave: - `poetry upgrade django`: Upgrade Django to the newest version that still works with other dependencies; equivalent to `poetry remove django; poetry add django`. - `poetry upgrade django djangorestframework`: As above, but with more than one package at a time. - `poetry upgrade django=^2.1`: Set the version of `django` to `^2.1`, equivalent to `poetry remove django; poetry add django=^2.1`. - `poetry upgrade`: Upgrade every dependency to the newest possible version. Equivalent to deleting the entire `[tool.poetry.dependencies]` section of `pyproject.toml` and running `poetry add` with a list of the names (but not versions) of every package

Comments (0)

No comments yet. Start the discussion.

Comment on this issue