--- - branch: MAIN date: Thu Oct 18 10:11:25 UTC 2018 files: - new: '1.61' old: '1.60' path: pkgsrc/devel/py-test/Makefile pathrev: pkgsrc/devel/py-test/Makefile@1.61 type: modified - new: '1.14' old: '1.13' path: pkgsrc/devel/py-test/PLIST pathrev: pkgsrc/devel/py-test/PLIST@1.14 type: modified - new: '1.56' old: '1.55' path: pkgsrc/devel/py-test/distinfo pathrev: pkgsrc/devel/py-test/distinfo@1.56 type: modified id: 20181018T101125Z.1c03441df9499e3fa529ae06027fb30ee1d405ae log: "py-test: updated to 3.9.1\n\npytest 3.9.1:\nFeatures\n- For test-suites containing test classes, the information about the subclassed module is now output only if a higher verbosity level is specified (at least 窶�-vv窶�).\n\npytest 3.9.0:\nDeprecations\n- The following accesses have been documented as deprecated for years, but are now actually emitting deprecation warnings.\nAccess of Module, Function, Class, Instance, File and Item through Node instances. Now users will this warning:\nusage of Function.Module is deprecated, please use pytest.Module instead\nUsers should just import pytest and access those objects using the pytest module.\nrequest.cached_setup, this was the precursor of the setup/teardown mechanism available to fixtures. You can consult funcarg comparison section in the docs.\nUsing objects named \"Class\" as a way to customize the type of nodes that are collected in Collector subclasses has been deprecated. Users instead should use pytest_collect_make_item to customize node types during collection.\nThis issue should affect only advanced plugins who create new collection types, so if you see this warning message please contact the authors so they can change the code.\nThe warning that produces the message below has changed to RemovedInPytest4Warning:\ngetfuncargvalue is deprecated, use getfixturevalue\n- Add a Deprecation warning for pytest.ensuretemp as it was deprecated since a while.\n\nFeatures\n- Improve usage errors messages by hiding internal details which can be distracting and noisy.\nThis has the side effect that some error conditions that previously raised generic errors (such as ValueError for unregistered marks) are now raising Failed exceptions.\n- Improve the error displayed when a conftest.py file could not be imported.\nIn order to implement this, a new chain parameter was added to ExceptionInfo.getrepr to show or hide chained tracebacks in Python 3 (defaults to True).\n- Add empty_parameter_set_mark=fail_at_collect ini option for raising an exception when parametrize collects an empty set.\n- Log messages generated in the collection phase are shown when live-logging is enabled and/or when they are logged to a file.\n- Introduce tmp_path as a fixture providing a Path object.\n- Deprecation warnings are now shown even if you customize the warnings filters yourself. In the previous version any customization would override pytest窶å\x86± filters and deprecation warnings would fall back to being hidden by default.\n- Allow specification of timeout for Testdir.runpytest_subprocess() and Testdir.run().\n- Add returncode argument to pytest.exit() to exit pytest with a specific return code.\n- Reimplement pytest.deprecated_call using pytest.warns so it supports the match='...' keyword argument.\nThis has the side effect that pytest.deprecated_call now raises pytest.fail.Exception instead of AssertionError.\n- Require setuptools>=30.3 and move most of the metadata to setup.cfg.\n\nBug Fixes\n- Improve error message when test functions of unittest.TestCase subclasses use a parametrized fixture.\n- request.fixturenames now correctly returns the name of fixtures created by request.getfixturevalue().\n- Warning filters passed as command line options using -W now take precedence over filters defined in ini configuration files.\n- Fix source reindenting by using textwrap.dedent directly.\n- pytest.warn will capture previously-warned warnings in Python 2. Previously they were never raised.\n- Resolve symbolic links for args.\nThis fixes running pytest tests/test_foo.py::test_bar, where tests is a symlink to project/app/tests: previously project/app/conftest.py would be ignored for fixtures then.\n- Fix duplicate printing of internal errors when using --pdb.\n- pathlib based tmpdir cleanup now correctly handles symlinks in the folder.\n- Display the filename when encountering SyntaxWarning.\n\nImproved Documentation\n- Update usefixtures documentation to clarify that it can窶å\x86² be used with fixture functions.\n- Update fixture documentation to specify that a fixture can be invoked twice in the scope it窶å\x86± defined for.\n- According to unittest.rst, setUpModule and tearDownModule were not implemented, but it turns out they are. So updated the documentation for unittest.\n- Add tempir testing example to CONTRIBUTING.rst guide\nTrivial/Internal Changes\n- The internal MarkerError exception has been removed.\n- Port the implementation of tmpdir to pathlib.\n- Exclude 0.00 second entries from --duration output unless -vv is passed on the command-line.\n- Fixed formatting of string literals in internal tests.\n" module: pkgsrc subject: 'CVS commit: pkgsrc/devel/py-test' unixtime: '1539857485' user: adam