Log message:
python: egg.mk: add USE_PKG_RESOURCES flag

This flag should be set for packages that import pkg_resources
and thus need setuptools after the build step.

Set this flag for packages that need it and bump PKGREVISION.

Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS

Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip

Log message:
devel: Remove SHA1 hashes for distfiles

Log message:
py-test: updated to 6.2.4

pytest 6.2.4
Bug Fixes
* Fixed assertion rewriting on Python 3.10.

Log message:
py-test: updated to 6.2.3

pytest 6.2.3 (2021-04-03)
=========================

Bug Fixes
---------

- pytest used to create directories under ``/tmp`` with world-readable
  permissions. This means that any user in the system was able to read
  information written by tests in temporary directories (such as those created by
  the ``tmp_path``/``tmpdir`` fixture). Now the directories are created with
  private permissions.

  pytest used silenty use a pre-existing ``/tmp/pytest-of-<username>`` \ 
directory,
  even if owned by another user. This means another user could pre-create such a
  directory and gain control of another user's temporary directory. Now such a
  condition results in an error.

Log message:
py-test: updated to 6.2.2

pytest 6.2.2

Bug Fixes
- Fixed "(<Skipped instance>)" being shown as a skip reason in \ 
the verbose test summary line when the reason is empty.
- Fix the ``faulthandler`` plugin for occasions when running with \ 
``twisted.logger`` and using ``pytest --capture=no``.

Log message:
py-test: updated to 6.2.1

pytest 6.2.1

Bug Fixes
Fixed bug where ImportPathMismatchError would be raised for files compiled in \ 
the host and loaded later from an UNC mounted path (Windows).

Fixed regression in approx: in 6.2.0 approx no longer raises TypeError when \ 
dealing with non-numeric types, falling back to normal comparison. Before 6.2.0, \ 
array types like tf.DeviceArray fell through to the scalar case, and happened to \ 
compare correctly to a scalar if they had only one element. After 6.2.0, these \ 
types began failing, because they inherited neither from standard Python number \ 
hierarchy nor from numpy.ndarray.

approx now converts arguments to numpy.ndarray if they expose the array protocol \ 
and are not scalars. This treats array-like objects like numpy arrays, \ 
regardless of size.

Log message:
py-test: updated to 6.2.0

pytest 6.2.0 (2020-12-12)
=========================

Breaking Changes
----------------
- pytest now supports python3.6+ only.

Deprecations
------------
- Directly constructing/calling the following classes/functions is now deprecated:
  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation \ 
warning, which may become a hard error in pytest 7.0.0.

- The ``--strict`` command-line option has been deprecated, use \ 
``--strict-markers`` instead.

  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 ``@pytest.yield_fixture`` decorator/function is now deprecated. Use \ 
:func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so \ 
can be search/replaced safely.

Features
--------
- pytest now warns about unraisable exceptions and unhandled thread exceptions \ 
that occur in tests on Python>=3.8.
  See :ref:`unraisable` for more information.
- New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but \ 
its methods return :class:`pathlib.Path` when appropriate instead of \ 
``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, \ 
in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir <_pytest.pytester.Testdir>` is now a \ 
thin wrapper around :class:`Pytester <_pytest.pytester.Pytester>`, \ 
preserving the old interface.

- A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the "global" variables \ 
available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

     def pytest_markeval_namespace():
         return {"color": "red"}

  ``test_func.py``:

  .. code-block:: python

     @pytest.mark.skipif("color == 'blue'", reason="Color is not \ 
red")
     def test_func():
         assert False

- It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly \ 
as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously \ 
some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context <pytest.MonkeyPatch.context>` \ 
is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the \ 
recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an \ 
instance created directly
  is not ``undo()``-ed automatically.

Improvements
------------
- Added an ``__str__`` implementation to the \ 
:class:`~pytest.pytester.LineMatcher` class which is returned from \ 
``pytester.run_pytest().stdout`` and similar. It returns the entire output, like \ 
the existing ``str()`` method.
- Verbose mode now shows the reason that a test was skipped in the test's \ 
terminal line after the "SKIPPED", "XFAIL" or \ 
"XPASS".
- The types of builtin pytest fixtures are now exported so they may be used in \ 
type annotations of test functions.
  The newly-exported types are:
  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and \ 
:fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and \ 
:fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only \ 
meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in \ 
pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at \ 
runtime, but is detected by type-checkers such as mypy.

- When a comparison between :func:`namedtuple <collections.namedtuple>` \ 
instances of the same type fails, pytest now shows the differing field names \ 
(possibly nested) instead of their indexes.
- :meth:`Node.warn <_pytest.nodes.Node.warn>` now permits any subclass of \ 
:class:`Warning`, not just :class:`PytestWarning <pytest.PytestWarning>`.
- Improved reporting when using ``--collected-only``. It will now show the \ 
number of collected tests in the summary stats.
- Use strict equality comparison for non-numeric types in :func:`pytest.approx` \ 
instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a \ 
supported feature.

- New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.
- Added ``'node_modules'`` to default value for :confval:`norecursedirs`.
- :meth:`doClassCleanups <unittest.TestCase.doClassCleanups>` (introduced \ 
in :mod:`unittest` in Python and 3.8) is now called appropriately.

Bug Fixes
---------
- Fixed quadratic behavior and improved performance of collection of items using \ 
autouse fixtures and xunit fixtures.
- Fixed an issue where some files in packages are getting lost from ``--lf`` \ 
even though they contain tests that failed. Regressed in pytest 5.4.0.
-  Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now \ 
considered stale after 3 days without modification (previous value was 3 hours) \ 
to avoid deleting directories still in use in long running test suites.
-  Fixed a crash or hang in :meth:`pytester.spawn \ 
<_pytest.pytester.Pytester.spawn>` when the :mod:`readline` module is \ 
involved.
- Fixed handling of recursive symlinks when collecting tests.
- Fixed symlinked directories not being followed during collection. Regressed in \ 
pytest 6.1.0.
- Fixed only one doctest being collected when using ``pytest --doctest-modules \ 
path/to/an/__init__.py``.

Improved Documentation
----------------------
- Add more information and use cases about skipping doctests.
- Classes which should not be inherited from are now marked ``final class`` in \ 
the API reference.
- ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and \ 
``"string"``.
- In pull request section, ask to commit after editing changelog and authors file.

Trivial/Internal Changes
------------------------
- The ``attrs`` dependency requirement is now >=19.2.0 instead of >=17.4.0.
- `.pyc` files created by pytest's assertion rewriting now conform to the newer \ 
PEP-552 format on Python>=3.7.
  (These files are internal and only interpreted by pytest itself.)

Log message:
py-test: updated to 6.1.2

pytest 6.1.2

Bug Fixes
* Fixed an issue where some files in packages are getting lost from --lf even \ 
though they contain tests that failed. Regressed in pytest 5.4.0.
* Directories created by tmpdir are now considered stale after 3 days without \ 
modification (previous value was 3 hours) to avoid deleting directories still in \ 
use in long running test suites.

Improved Documentation
* Improve deprecation warning message for pytest._fillfuncargs().