Fixes pytest warning about deprecated use --strict in setup.cfg

[kloczek]

Fixes pytest warning reported in #192

../../../../../usr/lib/python3.8/site-packages/_pytest/config/init.py:1183
/usr/lib/python3.8/site-packages/_pytest/config/init.py:1183: PytestDeprecationWarning: The --strict option is deprecated, use --strict-markers instead.
self.issue_config_time_warning(

Based on pytest-dev/pytest#8668

Signed-off-by: Tomasz Kłoczko kloczek@github.com

[temoto]

@kloczek it fails because requirements-test.txt specifies pytest==3.2.1 which doesn't support strict-markers yet.

[kloczek]

pytest==3.2.1 is really ancient version :/
Latest one which I'm usinng is 6.2.4.

[temoto]

Having that ancient version in separate environment will not hurt the other pytest you are using.

As of today (2021-05) httplib2 is not tested by external any pytest. It is tested using script/test in repo. script/test creates by default, or uses existing python environment and installs requirements-test.txt into it. This way there is a guarantee that what was tested on CI server will also be run tested exactly same way on any developer machine.

I'm fine with upgrading pytest in requirements-test.txt if there is a good reason.

For any patch to be merged, it must pass CI tests.

[temoto]

Thanks, this fix is merged in master.