`remove` not smart enough to detect depencency type

On other dependency managers, namely npm and yarn which I use the most, removeing a dependency removes it from whatever dependency list it’s in, be it runtime, development, peer or another dependency type, while poetry requires remove -D <package> to remove from dev deps.

I suggest that remove is made smart enough to remove the package name from any dependency list instead.

[sdispater]

@ranisalt Sometimes you might want to specify a dependency twice: in runtime and in dev. There are some valid reasons for that, like setting the dependency with extras in development:

[tool.poetry.dependencies]
python = "^3.6"
requests = "^2.19"

[tool.poetry.dev-dependencies]
requests = { version = "^2.19", extras = ["security"] }

[stale[bot]]

Closing this issue automatically because it has not had any activity since it has been marked as stale. If you think it is still relevant and should be addressed, feel free to open a new one.