Add plugin configuration through pyproject.toml? about pytest-mypy-plugins HOT 5 OPEN

Does --mypy-pyproject-toml-file not work for you?

from pytest-mypy-plugins.

The problem would remain the same. Sorry if my description of the issue is not clear.
It's not about using mypy.ini or pyproject.toml, that's not really relevant here.

To put it more simply, I would like to configure pytest-mypy-plugins itself through pyproject.toml instead of using command-line options.

This would prevent tests from passing or failing depending on the current working directory, due to the way relative paths are resolved for --mypy-pyproject-toml-file and --mypy-ini-file.

from pytest-mypy-plugins.

Oh, I see :)
PR is welcome!

from pytest-mypy-plugins.

Great, thanks! I'll work on it.

from pytest-mypy-plugins.

Nice! I'm in the process of adding this plugin to the cattrs test suite and I think I want this.

To explain my use case: I want to run Mypy only on a single version of Python, say the latest. It's good enough and keeps complexity down. But I need to use --mypy-only-local-stub.

So my plan was to install the plugin only on 3.12 and put --mypy-only-local-stub into pyproject.toml/[tool.pytest.ini_options].addopts. But if I do that, on other Pythons pytest doesn't know what that argument is and won't run.

I'm sure there are other ways of solving this but this seemed like the simplest/most correct to me.

from pytest-mypy-plugins.