Log message:
py-test: updated to 6.1.1

pytest 6.1.1 (2020-10-03)
=========================

Bug Fixes
---------
- Fixed regression in pytest 6.1.0 causing incorrect rootdir to be determined in \ 
some non-trivial cases where parent directories have config files as well.
- Fixed crash in header reporting when :confval:`testpaths` is used and contains \ 
absolute paths (regression in 6.1.0).

pytest 6.1.0 (2020-09-26)
=========================

Breaking Changes
----------------

- As per our policy, the following features which have been deprecated in the \ 
5.X series are now
  removed:
  * The ``funcargnames`` read-only property of ``FixtureRequest``, ``Metafunc``, \ 
and ``Function`` classes. Use ``fixturenames`` attribute.
  * ``@pytest.fixture`` no longer supports positional arguments, pass all \ 
arguments by keyword instead.
  * Direct construction of ``Node`` subclasses now raise an error, use \ 
``from_parent`` instead.
  * The default value for ``junit_family`` has changed to ``xunit2``. If you \ 
require the old format, add ``junit_family=xunit1`` to your configuration file.
  * The ``TerminalReporter`` no longer has a ``writer`` attribute. Plugin \ 
authors may use the public functions of the ``TerminalReporter`` instead of \ 
accessing the ``TerminalWriter`` object directly.
  * The ``--result-log`` option has been removed. Users are recommended to use \ 
the `pytest-reportlog <https://github.com/pytest-dev/pytest-reportlog>`__ \ 
plugin instead.

  For more information consult
  `Deprecations and Removals \ 
<https://docs.pytest.org/en/stable/deprecations.html>`__ in the docs.

Deprecations
------------
- The ``pytest.collect`` module is deprecated: all its names can be imported \ 
from ``pytest`` directly.
- The ``pytest._fillfuncargs`` function is deprecated. This function was kept
  for backward compatibility with an older plugin.

  It's functionality is not meant to be used directly, but if you must replace
  it, use `function._request._fillfixtures()` instead, though note this is not
  a public API and may break in the future.

- The special ``-k '-expr'`` syntax to ``-k`` is deprecated. Use ``-k 'not expr'``
  instead.

  The special ``-k 'expr:'`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.

- The :func:`pytest_warning_captured \ 
<_pytest.hookspec.pytest_warning_captured>` hook is deprecated in favor
  of :func:`pytest_warning_recorded \ 
<_pytest.hookspec.pytest_warning_recorded>`, and will be removed in a \ 
future version.
- The ``gethookproxy()`` and ``isinitpath()`` methods of ``FSCollector`` and \ 
``Package`` are deprecated;
  use ``self.session.gethookproxy()`` and ``self.session.isinitpath()`` instead.
  This should work on all pytest versions.

Features
--------
- New ``--durations-min`` command-line flag controls the minimal duration for \ 
inclusion in the slowest list of tests shown by ``--durations``. Previously this \ 
was hard-coded to ``0.005s``.

Improvements
------------
- Internal pytest warnings issued during the early stages of initialization are \ 
now properly handled and can filtered through :confval:`filterwarnings` or \ 
``--pythonwarnings/-W``.
- When a plugin listed in ``required_plugins`` is missing or an unknown config \ 
key is used with ``--strict-config``, a simple error message is now shown \ 
instead of a stacktrace.
-  Added two new attributes :attr:`rootpath \ 
<_pytest.config.Config.rootpath>` and :attr:`inipath \ 
<_pytest.config.Config.inipath>` to :class:`Config \ 
<_pytest.config.Config>`.
  These attributes are :class:`pathlib.Path` versions of the existing \ 
:attr:`rootdir <_pytest.config.Config.rootdir>` and :attr:`inifile \ 
<_pytest.config.Config.inifile>` attributes,
  and should be preferred over them when possible.

- Public classes which are not designed to be inherited from are now marked \ 
`@final <https://docs.python.org/3/library/typing.html#typing.final>`_.
  Code which inherits from these classes will trigger a type-checking (e.g. \ 
mypy) error, but will still work in runtime.
  Currently the ``final`` designation does not appear in the API Reference but \ 
hopefully will in the future.

Bug Fixes
---------
- Fixed error when overwriting a parametrized fixture, while also reusing the \ 
super fixture value.

  .. code-block:: python

      # conftest.py
      import pytest

      @pytest.fixture(params=[1, 2])
      def foo(request):
          return request.param

      # test_foo.py
      import pytest

      @pytest.fixture
      def foo(foo):
          return foo * 2

- Fixed an internal error crash with ``IndexError: list index out of range`` when
  collecting a module which starts with a decorated function, the decorator
  raises, and assertion rewriting is enabled.
- pylint shouldn't complain anymore about unimplemented abstract methods when \ 
inheriting from :ref:`File <non-python tests>`.
- Fixed test collection when a full path without a drive letter was passed to \ 
pytest on Windows (for example ``\projects\tests\test.py`` instead of \ 
``c:\projects\tests\pytest.py``).
- Fix handling of command-line options that appear as paths but trigger an \ 
OS-level syntax error on Windows, such as the options used internally by \ 
``pytest-xdist``.
- Fixed INTERNALERROR when accessing locals / globals with faulty ``exec``.

Improved Documentation
----------------------
- Removed faq.rst and its reference in contents.rst.

Trivial/Internal Changes
------------------------
- The internal ``junitxml`` plugin has rewritten to use ``xml.etree.ElementTree``.
  The order of attributes in XML elements might differ. Some unneeded escaping is
  no longer performed.
- The dependency on the ``more-itertools`` package has been removed.
- The result type of :meth:`capfd.readouterr() \ 
<_pytest.capture.CaptureFixture.readouterr>` (and similar) is no longer a \ 
namedtuple,
  but should behave like one in all respects. This was done for technical reasons.
- When collecting tests, pytest finds test classes and functions by examining the
  attributes of python objects (modules, classes and instances). To speed up this
  process, pytest now ignores builtin attributes (like ``__class__``,
  ``__delattr__`` and ``__new__``) without consulting the \ 
:confval:`python_classes` and
  :confval:`python_functions` configuration options and without passing them to \ 
plugins
  using the :func:`pytest_pycollect_makeitem \ 
<_pytest.hookspec.pytest_pycollect_makeitem>` hook.

Log message:
py-test: updated to 6.0.2

pytest 6.0.2
Bug Fixes
* Fixed --log-cli potentially causing unrelated print output to be swallowed.
* Fixed log-capturing level restored incorrectly if caplog.set_level is called \ 
more than once.
* Fixed NotSetType.token being used as the parameter ID when the parametrization \ 
list is empty. Regressed in pytest 6.0.0.
* Fix internal error when handling some exceptions that contain multiple lines \ 
or the style uses multiple lines (--tb=line for example).

Log message:
devel/py-test: Back out previous.

Apparently a package cannot TEST_DEPENDS on itself, even if it is
necessary in order for make test to work.  The TEST_DEPENDS mechanism
seems like it could maybe use some work.

Log message:
devel/py-test: Needs itself installed to run its own tests.

Log message:
py-test: updated to 6.0.1

pytest 6.0.1

Bug Fixes
* Passing an empty help value to Parser.add_option is now accepted instead of \ 
crashing when running pytest --help. Passing None raises a more informative \ 
TypeError.
* Fix pylint not-callable lint on pytest.mark.parametrize() and the other \ 
builtin marks: skip, skipif, xfail, usefixtures, filterwarnings.
* Fix regression in plugins using TestReport.longreprtext (such as pytest-html) \ 
when TestReport.longrepr is not a string.
* Fix logging capture handler's level not reset on teardown after a call to \ 
caplog.set_level().

pytest 6.0.0

(Please see the full set of changes for this release also in the 6.0.0rc1 notes \ 
below)

Breaking Changes

* PytestDeprecationWarning are now errors by default.

Following our plan to remove deprecated features with as little disruption as \ 
possible, all warnings of type PytestDeprecationWarning now generate errors \ 
instead of warning messages.

The affected features will be effectively removed in pytest 6.1, so please \ 
consult the Deprecations and Removals section in the docs for directions on how \ 
to update existing code.

In the pytest 6.0.X series, it is possible to change the errors back into \ 
warnings as a stopgap measure by adding this to your pytest.ini file:

[pytest]
filterwarnings =
    ignore::pytest.PytestDeprecationWarning
But this will stop working when pytest 6.1 is released.

* The exec_() and is_true() methods of _pytest._code.Frame have been removed.

Features
* Added support for :envvar:`NO_COLOR` and :envvar:`FORCE_COLOR` environment \ 
variables to control colored output.

Improvements
* --log-file CLI option and log_file ini marker now create subdirectories if needed.
* The :func:`pytest.raises` function has a clearer error message when match \ 
equals the obtained string but is not a regex match. In this case it is \ 
suggested to escape the regex.
Bug Fixes

* Fix the reported location of tests skipped with @pytest.mark.skip when \ 
--runxfail is used.
* :fixture:`tmpdir` and :fixture:`tmp_path` no longer raise an error if the lock \ 
to check for stale temporary directories is not accessible.
* Preserve line endings when captured via capfd.
* Restored the previous formatting of TracebackEntry.__str__ which was changed \ 
by accident.

Improved Documentation
* Clarified when the usefixtures mark can apply fixtures to test.
* Add a note about -q option used in getting started guide.

Trivial/Internal Changes
* Fixture scope package is no longer considered experimental.

pytest 6.0.0rc1

Breaking Changes

* TestReport.longrepr is now always an instance of ReprExceptionInfo. Previously \ 
it was a str when a test failed with pytest.fail(..., pytrace=False).

* symlinks are no longer resolved during collection and matching conftest.py \ 
files with test file paths.

Resolving symlinks for the current directory and during collection was \ 
introduced as a bugfix in 3.9.0, but it actually is a new feature which had \ 
unfortunate consequences in Windows and surprising results in other platforms.

This might break test suites which made use of this feature; the fix is to \ 
create a symlink for the entire test tree, and not only to partial files/tress \ 
as it was possible previously.

* Testdir.run().parseoutcomes() now always returns the parsed nouns in plural form.

Originally parseoutcomes() would always returns the nouns in plural form, but a \ 
change meant to improve the terminal summary by using singular form single items \ 
(1 warning or 1 error) caused an unintended regression by changing the keys \ 
returned by parseoutcomes().

Now the API guarantees to always return the plural form, so calls like this:

result = testdir.runpytest()
result.assert_outcomes(error=1)
Need to be changed to:

result = testdir.runpytest()
result.assert_outcomes(errors=1)
* The os.dup() function is now assumed to exist. We are not aware of any \ 
supported Python 3 implementations which do not provide it.

* -k no longer matches against the names of the directories outside the test \ 
session root.

Also, pytest.Package.name is now just the name of the directory containing the \ 
package's __init__.py file, instead of the full path. This is consistent with \ 
how the other nodes are named, and also one of the reasons why -k would match \ 
against any directory containing the test suite.

* Expressions given to the -m and -k options are no longer evaluated using \ 
Python's :func:`eval`. The format supports or, and, not, parenthesis and general \ 
identifiers to match against. Python constants, keywords or other operators are \ 
no longer evaluated differently.

* Pytest now uses its own TerminalWriter class instead of using the one from the \ 
py library. Plugins generally access this class through TerminalReporter.writer, \ 
TerminalReporter.write() (and similar methods), or \ 
_pytest.config.create_terminal_writer().

The following breaking changes were made:

Output (write() method and others) no longer flush implicitly; the flushing \ 
behavior of the underlying file is respected. To flush explicitly (for example, \ 
if you want output to be shown before an end-of-line is printed), use \ 
write(flush=True) or terminal_writer.flush().
Explicit Windows console support was removed, delegated to the colorama library.
Support for writing bytes was removed.
The reline method and chars_on_current_line property were removed.
The stringio and encoding arguments was removed.
Support for passing a callable instead of a file was removed.
* The item.catch_log_handler and item.catch_log_handlers attributes, set by the \ 
logging plugin and never meant to be public, are no longer available.

The deprecated --no-print-logs option and log_print ini option are removed. Use \ 
--show-capture instead.

* Removed the unused args parameter from pytest.Function.__init__.

* Removed the pytest_doctest_prepare_content hook specification. This hook \ 
hasn't been triggered by pytest for at least 10 years.

* Some changes were made to the internal _pytest._code.source, listed here for \ 
the benefit of plugin authors who may be using it:

The deindent argument to Source() has been removed, now it is always true.
Support for zero or multiple arguments to Source() has been removed.
Support for comparing Source with an str has been removed.
The methods Source.isparseable() and Source.putaround() have been removed.
The method Source.compile() and function _pytest._code.compile() have been \ 
removed; use plain compile() instead.
The function _pytest._code.source.getsource() has been removed; use Source() \ 
directly instead.

Deprecations
* The special -k '-expr' syntax to -k is deprecated. Use -k 'not expr' instead.
The special -k 'expr:' syntax to -k is deprecated. Please open an issue if you \ 
use this and want a replacement.
* pytest_warning_captured is deprecated in favor of the pytest_warning_recorded hook.

Features
* pytest now supports pyproject.toml files for configuration.

The configuration options is similar to the one available in other formats, but \ 
must be defined in a [tool.pytest.ini_options] table to be picked up by pytest:

# pyproject.toml
[tool.pytest.ini_options]
minversion = "6.0"
addopts = "-ra -q"
testpaths = [
    "tests",
    "integration",
]
More information can be found in the docs.

* pytest now includes inline type annotations and exposes them to user programs. \ 
Most of the user-facing API is covered, as well as internal code.

If you are running a type checker such as mypy on your tests, you may start \ 
noticing type errors indicating incorrect usage. If you run into an error that \ 
you believe to be incorrect, please let us know in an issue.

The types were developed against mypy version 0.780. Versions before 0.750 are \ 
known not to work. We recommend using the latest version. Other type checkers \ 
may work as well, but they are not officially verified to work by pytest yet.

* Introduced a new hook named pytest_warning_recorded to convey information \ 
about warnings captured by the internal pytest warnings plugin.

This hook is meant to replace pytest_warning_captured, which is deprecated and \ 
will be removed in a future release.

* New command-line flags:

--no-header: disables the initial header, including platform, version, and plugins.
--no-summary: disables the final test summary, including warnings.
* A warning is now shown when an unknown key is read from a config INI file.

The --strict-config flag has been added to treat these warnings as errors.

* Added --code-highlight command line option to enable/disable code highlighting \ 
in terminal output.
* New --import-mode=importlib option that uses importlib to import test modules.

Traditionally pytest used __import__ while changing sys.path to import test \ 
modules (which also changes sys.modules as a side-effect), which works but has a \ 
number of drawbacks, like requiring test modules that don't live in packages to \ 
have unique names (as they need to reside under a unique name in sys.modules).

--import-mode=importlib uses more fine grained import mechanisms from importlib \ 
which don't require pytest to change sys.path or sys.modules at all, eliminating \ 
much of the drawbacks of the previous mode.

You can read more about this option in the documentation.
* New required_plugins configuration option allows the user to specify a list of \ 
plugins, including version information, that are required for pytest to run. An \ 
error is raised if any required plugins are not found when running pytest.

Improvements
* The pytest command now suppresses the BrokenPipeError error message that is \ 
printed to stderr when the output of pytest is piped and and the pipe is closed \ 
by the piped-to program (common examples are less and head).
* Improved precision of test durations measurement. CallInfo items now have a \ 
new <CallInfo>.duration attribute, created using time.perf_counter(). This \ 
attribute is used to fill the <TestReport>.duration attribute, which is \ 
more accurate than the previous <CallInfo>.stop - <CallInfo>.start \ 
(as these are based on time.time()).
* Rich comparison for dataclasses and attrs-classes is now recursive.
* Exposed the pytest.FixtureLookupError exception which is raised by \ 
request.getfixturevalue() (where request is a FixtureRequest fixture) when a \ 
fixture with the given name cannot be returned.
* If an error is encountered while formatting the message in a logging call, for \ 
example logging.warning("oh no!: %s: %s", "first") (a second \ 
argument is missing), pytest now propagates the error, likely causing the test \ 
to fail.
Previously, such a mistake would cause an error to be printed to stderr, which \ 
is not displayed by default for passing tests. This change makes the mistake \ 
visible during testing.
You may supress this behavior temporarily or permanently by setting \ 
logging.raiseExceptions = False.
* Explicit new-lines in help texts of command-line options are preserved, \ 
allowing plugins better control of the help displayed to users.
* When using the --duration option, the terminal message output is now more \ 
precise about the number and duration of hidden items.
* Collected files are displayed after any reports from hooks, e.g. the status \ 
from --lf.
* When fd capturing is used, through --capture=fd or the capfd and capfdbinary \ 
fixtures, and the file descriptor (0, 1, 2) cannot be duplicated, FD capturing \ 
is still performed. Previously, direct writes to the file descriptors would fail \ 
or be lost in this case.
* Exit with an error if the --basetemp argument is empty, is the current working \ 
directory or is one of the parent directories. This is done to protect against \ 
accidental data loss, as any directory passed to this argument is cleared.
* pytest --version now displays just the pytest version, while pytest --version \ 
--version displays more verbose information including plugins. This is more \ 
consistent with how other tools show --version.
* :meth:`caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level>` \ 
will now override any :confval:`log_level` set via the CLI or configuration \ 
file.
* :meth:`caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level>` \ 
and :meth:`caplog.at_level() <_pytest.logging.LogCaptureFixture.at_level>` \ 
no longer affect the level of logs that are shown in the Captured log report \ 
report section.
* Improve recursive diff report for comparison asserts on dataclasses / attrs.
* --junitxml now includes the exception cause in the message XML attribute for \ 
failures during setup and teardown.

Previously:
<error message="test setup failure">
Now:
<error message="failed on setup with &quot;ValueError: Some error \ 
during setup&quot;">

Bug Fixes
* Fix issue where directories from :fixture:`tmpdir` are not removed properly \ 
when multiple instances of pytest are running in parallel.
* Prevent crashing and provide a user-friendly error when a marker expression \ 
(-m) invoking of :func:`eval` raises any exception.
* The path shown in the summary report for SKIPPED tests is now always relative. \ 
Previously it was sometimes absolute.
* Fix a possible race condition when trying to remove lock files used to control \ 
access to folders created by :fixture:`tmp_path` and :fixture:`tmpdir`.
* Fixes an issue where logging during collection step caused duplication of log \ 
messages to stderr.
* Paths appearing in error messages are now correct in case the current working \ 
directory has changed since the start of the session.
* Support deleting paths longer than 260 characters on windows created inside \ 
:fixture:`tmpdir`.
* Fix crash with captured output when using :fixture:`capsysbinary`.
* Revert the change introduced by 6330, which required all arguments to \ 
@pytest.mark.parametrize to be explicitly defined in the function signature.

The intention of the original change was to remove what was expected to be an \ 
unintended/surprising behavior, but it turns out many people relied on it, so \ 
the restriction has been reverted.

* Fix crash when plugins return an unknown stats while using the --reportlog option.
* Ensure a unittest.IsolatedAsyncioTestCase is actually awaited.
* Fix TerminalRepr instances to be hashable again.
* Fix regression where functions registered with \ 
:meth:`unittest.TestCase.addCleanup` were not being called on test failures.
* Allow users to still set the deprecated TerminalReporter.writer attribute.
* Prevent pytest from printing ConftestImportFailure traceback to stdout.
* Fix regressions with --lf filtering too much since pytest 5.4.
* Revert "tmpdir: clean up indirection via config for factories" 6767 \ 
as it breaks pytest-xdist.
* When a yielding fixture fails to yield a value, report a test setup error \ 
instead of crashing.
* The path of file skipped by @pytest.mark.skip in the SKIPPED report is now \ 
relative to invocation directory. Previously it was relative to root directory.
* Fixed regression: asyncbase.TestCase tests are executed correctly again.
* --setup-show now doesn't raise an error when a bytes value is used as a \ 
parametrize parameter when Python is called with the -bb flag.
* Fix :meth:`pytest.File.from_parent` so it forwards extra keyword arguments to \ 
the constructor.
* Classes with broken __getattribute__ methods are displayed correctly during \ 
failures.
* Prevent hiding the underlying exception when ConfTestImportFailure is raised.
* Fix _is_setup_py for files encoded differently than locale.
* Fix regression where running with --pdb would call \ 
:meth:`unittest.TestCase.tearDown` for skipped tests.
* When using pytest.fixture on a function directly, as in pytest.fixture(func), \ 
if the autouse or params arguments are also passed, the function is no longer \ 
ignored, but is marked as a fixture.
* Fix possibly incorrect evaluation of string expressions passed to \ 
pytest.mark.skipif and pytest.mark.xfail, in rare circumstances where the exact \ 
same string is used but refers to different global values.
* Fixed exception causes all over the codebase, i.e. use raise new_exception \ 
from old_exception when wrapping an exception.

Improved Documentation
* The development guide now links to the contributing section of the docs and \ 
RELEASING.rst on GitHub.
* Add a note about --strict and --strict-markers and the preference for the \ 
latter one.
* Explain indirect parametrization and markers for fixtures.

Trivial/Internal Changes
* The originalname attribute of _pytest.python.Function now defaults to name if \ 
not provided explicitly, and is always set.
* The dependency on the wcwidth package has been removed.
* Replaced py.iniconfig with iniconfig.
* src/_pytest/config/__init__.py now uses the warnings module to report warnings \ 
instead of sys.stderr.write.
* Remove last internal uses of deprecated slave term from old pytest-xdist.
* py>=1.8.2 is now required.

Log message:
py-test: updated to 5.4.3

pytest 5.4.3:

Bug Fixes
* Paths appearing in error messages are now correct in case the current working \ 
directory has changed since the start of the session.
* Support deleting paths longer than 260 characters on windows created inside tmpdir.
* Prevent pytest from printing ConftestImportFailure traceback to stdout.
* Prevent hiding the underlying exception when ConfTestImportFailure is raised.
* Fix regression where running with --pdb would call the tearDown methods of \ 
unittest.TestCase subclasses for skipped tests.

Log message:
Make explicit python version test more robust.

Now if you come here looking for python27 it fails properly instead of
throwing a make syntax error.

Log message:
py-test: updated to 5.4.2

pytest 5.4.2:
Bug Fixes
* Fix crash with captured output when using the capsysbinary fixture.
* Ensure a unittest.IsolatedAsyncioTestCase is actually awaited.
* Fix TerminalRepr instances to be hashable again.
* Fix regression where functions registered with TestCase.addCleanup were not \ 
being called on test failures.
* Allow users to still set the deprecated TerminalReporter.writer attribute.
* Revert “tmpdir: clean up indirection via config for factories” 6767 as it \ 
breaks pytest-xdist.
* Fixed regression: asyncbase.TestCase tests are executed correctly again.
* Fix File.from_constructor so it forwards extra keyword arguments to the \ 
constructor.
* Classes with broken __getattribute__ methods are displayed correctly during \ 
failures.
* Fix _is_setup_py for files encoded differently than locale.

pytest 5.4.1:
Bug Fixes
* Revert the change introduced by 6330, which required all arguments to \ 
@pytest.mark.parametrize to be explicitly defined in the function signature.
The intention of the original change was to remove what was expected to be an \ 
unintended/surprising behavior, but it turns out many people relied on it, so \ 
the restriction has been reverted.
* Fix crash when plugins return an unknown stats while using the --reportlog option.

pytest 5.4.0:
Breaking Changes
* Matching of -k EXPRESSION to test names is now case-insensitive.
* Plugins specified with -p are now loaded after internal plugins, which results \ 
in their hooks being called before the internal ones.
This makes the -p behavior consistent with PYTEST_PLUGINS.
* Removed the long-deprecated pytest_itemstart hook.
This hook has been marked as deprecated and not been even called by pytest for \ 
over 10 years now.
* Reversed / fix meaning of “+/-” in error diffs. “-” means that sth. \ 
expected is missing in the result and “+” means that there are unexpected \ 
extras in the result.
* The cached_result attribute of FixtureDef is now set to None when the result \ 
is unavailable, instead of being deleted.
If your plugin performs checks like hasattr(fixturedef, 'cached_result'), for \ 
example in a pytest_fixture_post_finalizer hook implementation, replace it with \ 
fixturedef.cached_result is not None. If you del the attribute, set it to None \ 
instead.

Deprecations
* Option --no-print-logs is deprecated and meant to be removed in a future \ 
release. If you use --no-print-logs, please try out --show-capture and provide \ 
feedback.
--show-capture command-line option was added in pytest 3.5.0 and allows to \ 
specify how to display captured output when tests fail: no, stdout, stderr, log \ 
or all (the default).
* Deprecate the unused/broken pytest_collect_directory hook. It was misaligned \ 
since the removal of the Directory collector in 2010 and incorrect/unusable as \ 
soon as collection was split from test execution.
* Deprecate using direct constructors for Nodes.
Instead they are now constructed via Node.from_parent.
This transitional mechanism enables us to untangle the very intensely entangled \ 
Node relationships by enforcing more controlled creation/configuration patterns.
As part of this change, session/config are already disallowed parameters and as \ 
we work on the details we might need disallow a few more as well.
Subclasses are expected to use super().from_parent if they intend to expand the \ 
creation of Nodes.
* The TerminalReporter.writer attribute has been deprecated and should no longer \ 
be used. This was inadvertently exposed as part of the public API of that plugin \ 
and ties it too much with py.io.TerminalWriter.

Features
* New –capture=tee-sys option to allow both live printing and capturing of \ 
test output.
* Now all arguments to @pytest.mark.parametrize need to be explicitly declared \ 
in the function signature or via indirect. Previously it was possible to omit an \ 
argument if a fixture with the same name existed, which was just an accident of \ 
implementation and was not meant to be a part of the API.
* Changed default for -r to fE, which displays failures and errors in the short \ 
test summary. -rN can be used to disable it (the old behavior).
* New options have been added to the junit_logging option: log, out-err, and all.
* Excess warning summaries are now collapsed per file to ensure readable display \ 
of warning summaries.

Improvements
* pytest.mark.parametrize accepts integers for ids again, converting it to strings.
* Use “yellow” main color with any XPASSED tests.
* Revert “A warning is now issued when assertions are made for None”.
The warning proved to be less useful than initially expected and had quite a few \ 
false positive cases.
* tmpdir_factory.mktemp now fails when given absolute and non-normalized paths.
* The pytest_warning_captured hook now receives a location parameter with the \ 
code location that generated the warning.
* pytester: the testdir fixture respects environment settings from the \ 
monkeypatch fixture for inner runs.
* --fulltrace is honored with collection errors.
* Make --showlocals work also with --tb=short.
* Add support for matching lines consecutively with LineMatcher’s \ 
fnmatch_lines() and re_match_lines().
* Code is now highlighted in tracebacks when pygments is installed.
Users are encouraged to install pygments into their environment and provide \ 
feedback, because the plan is to make pygments a regular dependency in the \ 
future.
* Import usage error message with invalid -o option.
* pytest.mark.parametrize supports iterators and generators for ids.

Bug Fixes
* Add support for calling pytest.xfail() and pytest.importorskip() with doctests.
* --trace now works with unittests.
* Fixed some warning reports produced by pytest to point to the correct location \ 
of the warning in the user’s code.
* Fix --last-failed to collect new tests from files with known failures.
* Report PytestUnknownMarkWarning at the level of the user’s code, not pytest’s.
* Fix interaction with --pdb and unittests: do not use unittest’s TestCase.debug().
* Fix summary entries appearing twice when f/F and s/S report chars were used at \ 
the same time in the -r command-line option (for example -rFf).
The upper case variants were never documented and the preferred form should be \ 
the lower case.
* Fallback to green (instead of yellow) for non-last items without previous \ 
passes with colored terminal progress indicator.
* --disable-warnings is honored with -ra and -rA.
* Fix bug in the comparison of request key with cached key in fixture.
A construct if key == cached_key: can fail either because == is explicitly \ 
disallowed, or for, e.g., NumPy arrays, where the result of a == b cannot \ 
generally be converted to bool. The implemented fix replaces == with is.
* Make capture output streams .write() method return the same return value from \ 
original streams.
* Fix EncodedFile.writelines to call the underlying buffer’s writelines method.
* Fix internal crash when faulthandler starts initialized (for example with \ 
PYTHONFAULTHANDLER=1 environment variable set) and faulthandler_timeout defined \ 
in the configuration file.
* Fix node ids which contain a parametrized empty-string variable.
* Assertion rewriting hooks are (re)stored for the current item, which fixes \ 
them being still used after e.g. pytester’s testdir.runpytest etc.
* pytest.exit() is handled when emitted from the pytest_sessionfinish hook. This \ 
includes quitting from a debugger.
* When pytest.raises() is used as a function (as opposed to a context manager), \ 
a match keyword argument is now passed through to the tested function. \ 
Previously it was swallowed and ignored (regression in pytest 5.1.0).
* Do not display empty lines inbetween traceback for unexpected exceptions with \ 
doctests.
* The testdir fixture works within doctests now.

Improved Documentation
* Add list of fixtures to start of fixture chapter.
* Expand first sentence on fixtures into a paragraph.
Trivial/Internal Changes
* Remove usage of parser module, deprecated in Python 3.9.

Log message:
mk.mk? mk.

Log message:
*: use py-more-itertools via versioned_dependencies.mk