poetry update --no-dev removes dev dependencies

[DMRobertson]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).
  • No exception

• OS version and name: Fedora 35
• Poetry version:1.1.12
• Link of a Gist with the contents of your pyproject.toml file: See below

Issue

Suppose we have a project with runtime and development dependencies. We may want to try running the project with the newest version of all runtime dependencies, but without updating development dependencies. For example, in matrix-org/synapse#12472 I wanted to run typecheckers against the latest version of all runtime dependencies, without bumping the version of mypy in use.

One attempt I had to do this was to use poetry update --no-dev. This correctly updated my lockfile but removed all development dependencies---not what I expected!

For a minimal example: given the following pyproject.toml file

$ cat pyproject.toml 
[tool.poetry]
name = "example"
version = "0.1.0"
description = ""
authors = ["David Robertson <[email protected]>"]

[tool.poetry.dependencies]
python = "^3.7"
bottle = "*"

[tool.poetry.dev-dependencies]
black = "^22.3.0"

[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"

• poetry install. This should install bottle, black, and black's dependencies.
• poetry run pip list to confirm the contents of the venv.
• poetry update --no-dev. This removes black's dependencies, leaving only bottle behind.
• poetry run pip list to confirm the contents of the venv.

[DMRobertson]

I've just tried this on current master and can't reproduce the issue. It even warns me that --no-dev is deprecated. In any case, hopefully having the issue written up makes this behaviour searchable for those of us who don't want to live on the bleeding edge.

#3139 might be related?

[DMRobertson]

Came across this today, but this time with poetry install --no-dev. This comment in particular explains the behaviour in poetry 1.x.

[github-actions]

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.