Code Quality: Incremental adoption of mypy type checks

poetry and poetry-core are full type annotated and checking types by mypy is prepared. However these checks are deactivated for most of the modules.

In this ticket I like to invite everybody to pick one or more modules in poetry and poetry-core and fix errors reported by mypy. Please link any PR you are starting to this issue.

In process:

• https://github.com/python-poetry/poetry-core/pull/253
• https://github.com/python-poetry/poetry/pull/5262
• https://github.com/python-poetry/poetry/pull/5260
• https://github.com/python-poetry/poetry/pull/5258
• https://github.com/python-poetry/poetry/pull/5255
• https://github.com/python-poetry/poetry/pull/5399
• https://github.com/python-poetry/poetry/pull/5402

[dimbleby]

I intend no upset, I’m here because I think poetry is a good thing, and I’m nothing but grateful to those who’ve got us this far. Please be assured that I am not trying to knock or discourage anyone, my apologies if it seemed otherwise.

But yeah, my experience is that contributing to poetry generally is a slow business. Probably #4595 would have been a better place to talk about it though.

[tarun-jethwani]

Hi @abn, @finswimmer @branchvincent , I will take up poetry.mixology to solve for mypy errors, as there is already an open PR for poetry.console