deprecate pytest.config

[dmtucker]

Could someone please explain the difference of pytest.config.getoption vs request.config.getoption and whether one should be preferred? Both seem to work, but I am unable to find any documentation/history on them.

[pytestbot]

GitMate.io thinks the contributors most likely able to help are @nicoddemus, and @RonnyPfannschmidt.

[The-Compiler]

request.config and pytest.config give you the same config object. request.config is preferred, as pytest.config is kind of a cumbersome global. I actually thought it was deprecated, but off-hand I can't find any documentation on it.

[RonnyPfannschmidt]

reminds me that we should replace pytest.config with something that prints warnings about removal in 4.x

[dmtucker]

@The-Compiler @RonnyPfannschmidt Excellent, thank you for the clarification.
We can close this unless it'd be useful for tracking the addition of a removal warning.

[asmodehn]

Let me point you here to the documentation as a reason for using this feature : https://docs.pytest.org/en/reorganize-docs/example/simple.html#control-skipping-of-tests-according-to-command-line-option

How would I define a decorator to use an option if I need to access the config object ? As far as I understand request is not accessible in that context.

[RonnyPfannschmidt]

@asmodehn string based conditions have access to the config

also there is the option of implementing a more complete handling of the markers/deselection

[asottile]

via #4498