Remove deprecated `--strict` option
This commit is contained in:
parent
f4e7b0d6e0
commit
1f8b39ed32
|
@ -438,19 +438,6 @@ The proper fix is to change the `return` to an `assert`:
|
|||
assert foo(a, b) == result
|
||||
|
||||
|
||||
The ``--strict`` command-line option
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. deprecated:: 6.2
|
||||
|
||||
The ``--strict`` command-line option has been deprecated in favor of ``--strict-markers``, which
|
||||
better conveys what the option does.
|
||||
|
||||
We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing
|
||||
flag for all strictness related options (``--strict-markers`` and ``--strict-config``
|
||||
at the moment, more might be introduced in the future).
|
||||
|
||||
|
||||
The ``yield_fixture`` function/decorator
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
@ -470,6 +457,20 @@ an appropriate period of deprecation has passed.
|
|||
Some breaking changes which could not be deprecated are also listed.
|
||||
|
||||
|
||||
The ``--strict`` command-line option
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. deprecated:: 6.2
|
||||
.. versionremoved:: 8.0
|
||||
|
||||
The ``--strict`` command-line option has been deprecated in favor of ``--strict-markers``, which
|
||||
better conveys what the option does.
|
||||
|
||||
We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing
|
||||
flag for all strictness related options (``--strict-markers`` and ``--strict-config``
|
||||
at the moment, more might be introduced in the future).
|
||||
|
||||
|
||||
.. _cmdline-preparse-deprecated:
|
||||
|
||||
Implementing the ``pytest_cmdline_preparse`` hook
|
||||
|
|
|
@ -1319,11 +1319,6 @@ class Config:
|
|||
self._validate_plugins()
|
||||
self._warn_about_skipped_plugins()
|
||||
|
||||
if self.known_args_namespace.strict:
|
||||
self.issue_config_time_warning(
|
||||
_pytest.deprecated.STRICT_OPTION, stacklevel=2
|
||||
)
|
||||
|
||||
if self.known_args_namespace.confcutdir is None:
|
||||
if self.inipath is not None:
|
||||
confcutdir = str(self.inipath.parent)
|
||||
|
|
|
@ -46,10 +46,6 @@ YIELD_FIXTURE = PytestDeprecationWarning(
|
|||
"Use @pytest.fixture instead; they are the same."
|
||||
)
|
||||
|
||||
STRICT_OPTION = PytestRemovedIn8Warning(
|
||||
"The --strict option is deprecated, use --strict-markers instead."
|
||||
)
|
||||
|
||||
# This deprecation is never really meant to be removed.
|
||||
PRIVATE = PytestDeprecationWarning("A private pytest class or function was used.")
|
||||
|
||||
|
|
|
@ -67,25 +67,6 @@ def test_hookimpl_via_function_attributes_are_deprecated():
|
|||
assert record.filename == __file__
|
||||
|
||||
|
||||
def test_strict_option_is_deprecated(pytester: Pytester) -> None:
|
||||
"""--strict is a deprecated alias to --strict-markers (#7530)."""
|
||||
pytester.makepyfile(
|
||||
"""
|
||||
import pytest
|
||||
|
||||
@pytest.mark.unknown
|
||||
def test_foo(): pass
|
||||
"""
|
||||
)
|
||||
result = pytester.runpytest("--strict", "-Wdefault::pytest.PytestRemovedIn8Warning")
|
||||
result.stdout.fnmatch_lines(
|
||||
[
|
||||
"'unknown' not found in `markers` configuration option",
|
||||
"*PytestRemovedIn8Warning: The --strict option is deprecated, use --strict-markers instead.",
|
||||
]
|
||||
)
|
||||
|
||||
|
||||
def test_yield_fixture_is_deprecated() -> None:
|
||||
with pytest.warns(DeprecationWarning, match=r"yield_fixture is deprecated"):
|
||||
|
||||
|
|
Loading…
Reference in New Issue