I want to use --config-strict in a py2/py3 universal python project, but the flag is mis-handled in pytest v4

also pytest v4 should detect the bare minimum of pyproject.toml config options, to be able to let the operator know that they need to upgrade, eg:

[tool.pytest.ini_options]
minversion = "6.0"

should cause pytest 4 to fail

• a detailed description of the bug or suggestion
• output of pip list from the virtual environment you are using
• pytest and operating system versions
• minimal example if possible