Treat relative paths in config file relative to config file, not cwd

[blueyed]

When using mypy_path = src it should be treated relative to the config file (if any), not the current working directory.
This also applies to the default of cache_dir (.cache_dir), which currently gets created in the current working directory always.

I.e. a detected/found (project) config file could be treated as the root for options with relative defaults also.

As for mypy_path this could be achieved in the type callback, which then however would need the config file / root as a new argument:

mypy/mypy/config_parser.py

Line 75 in 84126ab

'mypy_path': lambda s: [expand_path(p.strip()) for p in re.split('[,:]', s)],

As for global user config files, it should treat relative files therein relative to it, but it should not be used as a root for default settings like cache_dir.

[hauntsaninja]

Closing, since we implemented #7968 (i.e. use something like files = $MYPY_CONFIG_FILE_DIR/script.py)

[hauntsaninja]

I thought about this again because of #9751 and I'm reopening:
a) This is how I would expect things to behave, so it's likely to be a continued stumbling block
b) When specifying files, prepending MYPY_CONFIG_FILE_DIR to each of them is a bit painful
c) While this would be a breaking change, I'd be pretty surprised if this affected many people (somewhat data informed; I've seen a fair number of mypy CI setups as part of mypy_primer)

[Greedquest]

Another possible approach, rather than to specify paths relative to the config file, would be to set the cwd for both discovering and interpreting config files to be the root of the package that mypy is being invoked from. That way:

• You wouldn't break the workflow of having a config file in your home path that specifies a default mypy_path of a stubs dir for all packages made by that user
  • e.g all the user's packages look like package_root/stubs so they put mypy_path=stubs in ~/.config/mypy/config to use this default package structure. They would then invoke mypy from the package_root dir. If you change then it becomes ~/.config/mypy/config/stubs which is ofc incorrect.
• A user could call mypy on a single module in a package and wouldn't have to pass --config-file if their config is at the root of the project, making ide versions slightly easier to implement.

[woutervh]

A similar issue was fixed in ruff: astral-sh/ruff#7958

When specifying relative path in a file, it should be relative to the location of that file, never to $CWD.
In an average project, I see .mypy_cache-directories all over the place.

This is in my current pyproject.toml:

[tool.mypy]
# cfr https://mypy.readthedocs.io/en/stable/config_file.html#using-a-pyproject-toml-file
# cache_dir is relative to $CWD, which is incorrect behaviour
# we set MYPY_CACHE_DIR in .env instead until https://github.com/python/mypy/issues/7967 is fixed
# cache_dir = "var/cache/mypy"

[tool.pytest.ini_options]
cache-dir = "var/cache/pytest"  # relative to pyproject.toml
...

[tool.ruff]
cache-dir = "var/cache/ruff"  # relative to pyproject.toml