[pkgsrc/trunk]: pkgsrc/devel/py-test py-test: updated to 4.5.0

[adam <adam%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/fa553212dbce
branches:  trunk
changeset: 395804:fa553212dbce
user:      adam <adam%pkgsrc.org@localhost>
date:      Tue May 14 07:42:01 2019 +0000

description:
py-test: updated to 4.5.0

pytest 4.5.0:

Features
- A warning is now emitted when unknown marks are used as a decorator.
  This is often due to a typo, which can lead to silently broken tests.
- Show XFail reason as part of JUnitXML message field.
- Messages from crash reports are displayed within test summaries now, truncated to the terminal width.
- New flag --strict-markers that triggers an error when unknown markers (e.g. those not registered using the markers option_ in the configuration file) are used in the test suite.
  The existing --strict option has the same behavior currently, but can be augmented in the future for additional checks.
- Assertion failure messages for sequences and dicts contain the number of different items now.
- Improve reporting with --lf and --ff (run-last-failure).
- The --cache-show option/action accepts an optional glob to show only matching cache entries.
- Standard input (stdin) can be given to pytester's Testdir.run() and Testdir.popen().
- The -r option learnt about A to display all reports (including passed ones) in the short test summary.
- The short test summary is displayed after passes with output (-rP).
- The --last-failed (--lf) option got smarter and will now skip entire files if all tests
  of that test file have passed in previous runs, greatly speeding up collection.
- Introduce new specific warning PytestWarning subclasses to make it easier to filter warnings based on the class, rather than on the message. The new subclasses are:
  * PytestAssertRewriteWarning
  * PytestCacheWarning
  * PytestCollectionWarning
  * PytestConfigWarning
  * PytestUnhandledCoroutineWarning
  * PytestUnknownMarkWarning
- New record_testsuite_property session-scoped fixture allows users to log <property> tags at the testsuite
  level with the junitxml plugin.
  The generated XML is compatible with the latest xunit standard, contrary to
  the properties recorded by record_property and record_xml_attribute.
- The default logging format has been changed to improve readability. Here is an
  example of a previous logging message::
      test_log_cli_enabled_disabled.py    3 CRITICAL critical message logged by test
  This has now become::
      CRITICAL root:test_log_cli_enabled_disabled.py:3 critical message logged by test
  The formatting can be changed through the log_format <https://docs.pytest.org/en/latest/reference.html#confval-log_format>__ configuration option.
- --fixtures now also shows fixture scope for scopes other than "function".

Bug Fixes
- Deselected items from plugins using pytest_collect_modifyitems as a hookwrapper are correctly reported now.
-  With usage errors exitstatus is set to EXIT_USAGEERROR in the pytest_sessionfinish hook now as expected.
- outcome.exit is not used with EOF in the pdb wrapper anymore, but only with quit.

Improved Documentation
- Expand docs on registering marks and the effect of --strict.

Trivial/Internal Changes
- logging.raiseExceptions is not set to False anymore.
- pytest now depends on wcwidth <https://pypi.org/project/wcwidth>__ to properly track unicode character sizes for more precise terminal output.
- pytester's Testdir.popen() uses stdout and stderr via keyword arguments with defaults now (subprocess.PIPE).
- The code for the short test summary in the terminal was moved to the terminal plugin.
- Improved validation of kwargs for various methods in the pytester plugin.
- record_property now emits a PytestWarning when used with junit_family=xunit2: the fixture generates
  property tags as children of testcase, which is not permitted according to the most
  recent schema <https://github.com/jenkinsci/xunit-plugin/blob/master/
  src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd>__.
- Pin pluggy to < 1.0 so we don't update to 1.0 automatically when
  it gets released: there are planned breaking changes, and we want to ensure
  pytest properly supports pluggy 1.0.

diffstat:

 devel/py-test/Makefile |   4 ++--
 devel/py-test/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (27 lines):

diff -r d472dd793fbf -r fa553212dbce devel/py-test/Makefile
--- a/devel/py-test/Makefile    Tue May 14 07:34:50 2019 +0000
+++ b/devel/py-test/Makefile    Tue May 14 07:42:01 2019 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.78 2019/05/09 11:59:31 adam Exp $
+# $NetBSD: Makefile,v 1.79 2019/05/14 07:42:01 adam Exp $
 
-DISTNAME=      pytest-4.4.2
+DISTNAME=      pytest-4.5.0
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME:S/py//}
 CATEGORIES=    devel python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=p/pytest/}
diff -r d472dd793fbf -r fa553212dbce devel/py-test/distinfo
--- a/devel/py-test/distinfo    Tue May 14 07:34:50 2019 +0000
+++ b/devel/py-test/distinfo    Tue May 14 07:42:01 2019 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.71 2019/05/09 11:59:31 adam Exp $
+$NetBSD: distinfo,v 1.72 2019/05/14 07:42:01 adam Exp $
 
-SHA1 (pytest-4.4.2.tar.gz) = ad7ecc3dc915176faf1807c47503460d8562f39d
-RMD160 (pytest-4.4.2.tar.gz) = ed0583c479699a80fcb7c408682d0045f96306e2
-SHA512 (pytest-4.4.2.tar.gz) = 14a5a93fef129f58f37686b39ae1bfa3a32bc81f7ee83b6f754e0d7f18e85c0c7f44f12651dc9b3eb2ff62ab4aca5665b33e1c319051c7d8e3d5e004047150ec
-Size (pytest-4.4.2.tar.gz) = 932427 bytes
+SHA1 (pytest-4.5.0.tar.gz) = 29388d841fc8db7afe0618566c116759ffc6d8ed
+RMD160 (pytest-4.5.0.tar.gz) = d8e29517c781a266381226b320308181f4d25958
+SHA512 (pytest-4.5.0.tar.gz) = cbffc6216f83491b1de241058315c116697bfaa5206b5f558192a7f861d43dd036d30d0d689bedae7bdee4f0258dd19ef5827c356e11863dd596a5fabe8249fc
+Size (pytest-4.5.0.tar.gz) = 943607 bytes