Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

i suffered a little bit today because the pytest subsystem doesn’t support the <https://docs.pytest.org/en/7.1.x/how-to/capture-warnings.html#controlling-warnings|filterwarnings ini option>. (this was only partially because of pants-- problem was that filerwarnings is more powerful than and <https://github.com/pytest-dev/pytest/issues/10687|different from> `-W` , but i had to use `-W` via pytest `args` in pants). is there any reason not to support all the <https://docs.pytest.org/en/7.1.x/reference/reference.html#ini-options-ref|built-in ini options> in pants? what about supporting just `filterwarnings` for now?

doesn’t pants pick up if you have a `pytest.ini` file? Or otherwise a pytest config section in a pyproject.toml file. Pants have this in theirs for instance:
```[tool.pytest.ini_options]
asyncio_mode = "auto"
markers = ["platform_specific_behavior"]```

oh, yes, i think i new this at some point but forgot :man-facepalming: . it wouldn’t be good to duplicate all the configuration options in the pants.toml: <https://www.pantsbuild.org/docs/reference-pytest#config_discovery>

<https://www.pantsbuild.org/docs/python-test-goal#config-files>