Files
python-pytest/python-pytest-doc.spec

65 lines
2.0 KiB
RPMSpec
Raw Normal View History

#
# spec file for package python-pytest-doc
#
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
Accepting request 636145 from home:mimi_vx:branches:devel:languages:python:pytest - update to 3.8.0 * Config.warn has been deprecated, it should be replaced by calls to the standard warnings.warn. * Node.warn now supports two signatures: + node.warn(PytestWarning("some message")): is now the recommended way to call this function. The warning instance must be a PytestWarning or subclass instance. + node.warn("CI", "some message"): this code/message form is now deprecated and should be converted to the warning instance form above. * RemovedInPytest4Warning and PytestExperimentalApiWarning are now part of the public API and should be accessed using pytest.RemovedInPytest4Warning and pytest.PytestExperimentalApiWarning. * @pytest.mark.filterwarnings second parameter is no longer regex-escaped, making it possible to actually use regular expressions to check the warning message. + Note: regex-escaping the match string was an implementation oversight that might break test suites which depend on the old behavior. * Internal pytest warnings are now issued using the standard warnings module, making it possible to use the standard warnings filters to manage those warnings. This introduces PytestWarning, PytestDeprecationWarning and RemovedInPytest4Warning warning types as part of the public API. * DeprecationWarning and PendingDeprecationWarning are now shown by default if no other warning filter is configured. This makes pytest more compliant with PEP-0506. See the docs for more info. * Warnings are now captured and displayed during test collection. * PYTEST_DISABLE_PLUGIN_AUTOLOAD environment variable disables plugin auto-loading when set. * Added the count option to console_output_style to enable displaying the progress as a count instead of a percentage. * Added support for ‘xfailed’ and ‘xpassed’ outcomes to the pytester.RunResult.assert_outcomes signature. OBS-URL: https://build.opensuse.org/request/show/636145 OBS-URL: https://build.opensuse.org/package/show/devel:languages:python:pytest/python-pytest?expand=0&rev=15
2018-09-17 09:46:23 +00:00
# Please submit bugfixes or comments via https://bugs.opensuse.org/
#
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name: python-pytest-doc
Version: 3.10.1
Release: 0
Summary: Documentation for python-pytest, a testing tool with autodiscovery
License: MIT
Group: Documentation/HTML
Accepting request 618559 from devel:languages:python:pytest - update to 3.6.2 - add python-mock to buildrequires - fix test command - add python_mock.patch to use stdlib mock library on py3 - Update to version 3.6.0 + Features * Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) * Now when ``@pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`#2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) * ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`#3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) * The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 OBS-URL: https://build.opensuse.org/request/show/618559 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pytest?expand=0&rev=37
2018-06-25 09:35:39 +00:00
URL: https://github.com/pytest-dev/pytest
2017-11-02 09:24:10 +00:00
Source: https://files.pythonhosted.org/packages/source/p/pytest/pytest-%{version}.tar.gz
BuildRequires: %{python_module hypothesis}
Accepting request 618559 from devel:languages:python:pytest - update to 3.6.2 - add python-mock to buildrequires - fix test command - add python_mock.patch to use stdlib mock library on py3 - Update to version 3.6.0 + Features * Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) * Now when ``@pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`#2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) * ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`#3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) * The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 OBS-URL: https://build.opensuse.org/request/show/618559 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pytest?expand=0&rev=37
2018-06-25 09:35:39 +00:00
BuildRequires: %{python_module pytest = %{version}}
2017-11-02 09:24:10 +00:00
BuildRequires: %{python_module setuptools_scm}
Accepting request 618559 from devel:languages:python:pytest - update to 3.6.2 - add python-mock to buildrequires - fix test command - add python_mock.patch to use stdlib mock library on py3 - Update to version 3.6.0 + Features * Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) * Now when ``@pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`#2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) * ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`#3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) * The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 OBS-URL: https://build.opensuse.org/request/show/618559 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pytest?expand=0&rev=37
2018-06-25 09:35:39 +00:00
BuildRequires: python-mock
BuildRequires: python-rpm-macros
2017-11-02 09:24:10 +00:00
BuildRequires: python3-Sphinx
BuildRequires: python3-sphinxcontrib-trio
Provides: %{python_module pytest-doc = %{version}}
BuildArch: noarch
%ifpython2
BuildRequires: python-funcsigs
%endif
%description
This package contains the documentation to pytest, a cross-project Python
testing tool.
%prep
%setup -q -n pytest-%{version}
%build
python3 setup.py build_sphinx
rm doc/build/html/.buildinfo
%install
# Only building documentation
Accepting request 618559 from devel:languages:python:pytest - update to 3.6.2 - add python-mock to buildrequires - fix test command - add python_mock.patch to use stdlib mock library on py3 - Update to version 3.6.0 + Features * Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) * Now when ``@pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`#2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) * ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`#3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) * The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 OBS-URL: https://build.opensuse.org/request/show/618559 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pytest?expand=0&rev=37
2018-06-25 09:35:39 +00:00
#Check here because in main package creates a buildcycle
%check
Accepting request 618559 from devel:languages:python:pytest - update to 3.6.2 - add python-mock to buildrequires - fix test command - add python_mock.patch to use stdlib mock library on py3 - Update to version 3.6.0 + Features * Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_. (`#3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) * Now when ``@pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`#2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) * Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.html#breakpoint-builtin>`_ for details. (`#3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) * ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`#3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) * The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 OBS-URL: https://build.opensuse.org/request/show/618559 OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/python-pytest?expand=0&rev=37
2018-06-25 09:35:39 +00:00
%{python_expand py.test-%{$python_bin_suffix}}
%files
%doc CHANGELOG.rst
%doc doc/build/html
%license LICENSE
%changelog