p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update docs

This commit is contained in:
Tyler Goodlet 2017-08-24 16:53:37 -04:00
parent 756db2131f
commit 9ab83083d1
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
_pytest/config.py
View File

@ -165,7 +165,7 @@ def _prepareconfig(args=None, plugins=None):
class PytestPluginManager(PluginManager): class PytestPluginManager(PluginManager):
""" """
Overwrites :py:class:`pluggy.PluginManager <_pytest.vendored_packages.pluggy.PluginManager>` to add pytest-specific Overwrites :py:class:`pluggy.PluginManager <_pytest._pluggy.PluginManager>` to add pytest-specific
functionality: functionality:
* loading plugins from the command line, ``PYTEST_PLUGIN`` env variable and * loading plugins from the command line, ``PYTEST_PLUGIN`` env variable and
@ -203,7 +203,7 @@ class PytestPluginManager(PluginManager):
""" """
.. deprecated:: 2.8 .. deprecated:: 2.8
Use :py:meth:`pluggy.PluginManager.add_hookspecs <_pytest.vendored_packages.pluggy.PluginManager.add_hookspecs>` Use :py:meth:`pluggy.PluginManager.add_hookspecs <_pytest._pluggy.PluginManager.add_hookspecs>`
instead. instead.
""" """
warning = dict(code="I2", warning = dict(code="I2",

8
doc/en/writing_plugins.rst
View File

@ -454,7 +454,7 @@ hook wrappers and passes the same arguments as to the regular hooks.
At the yield point of the hook wrapper pytest will execute the next hook At the yield point of the hook wrapper pytest will execute the next hook
implementations and return their result to the yield point in the form of implementations and return their result to the yield point in the form of
a :py:class:`CallOutcome <_pytest.vendored_packages.pluggy._CallOutcome>` instance which encapsulates a result or a :py:class:`CallOutcome <_pytest._pluggy._CallOutcome>` instance which encapsulates a result or
exception info. The yield point itself will thus typically not raise exception info. The yield point itself will thus typically not raise
exceptions (unless there are bugs). exceptions (unless there are bugs).
@ -519,7 +519,7 @@ Here is the order of execution:
Plugin1). Plugin1).
4. Plugin3's pytest_collection_modifyitems then executing the code after the yield 4. Plugin3's pytest_collection_modifyitems then executing the code after the yield
point. The yield receives a :py:class:`CallOutcome <_pytest.vendored_packages.pluggy._CallOutcome>` instance which encapsulates point. The yield receives a :py:class:`CallOutcome <_pytest._pluggy._CallOutcome>` instance which encapsulates
the result from calling the non-wrappers. Wrappers shall not modify the result. the result from calling the non-wrappers. Wrappers shall not modify the result.
It's possible to use ``tryfirst`` and ``trylast`` also in conjunction with It's possible to use ``tryfirst`` and ``trylast`` also in conjunction with
@ -716,7 +716,7 @@ Reference of objects involved in hooks
:members: :members:
:inherited-members: :inherited-members:
.. autoclass:: _pytest.vendored_packages.pluggy._CallOutcome() .. autoclass:: _pytest._pluggy._CallOutcome()
:members: :members:
.. autofunction:: _pytest.config.get_plugin_manager() .. autofunction:: _pytest.config.get_plugin_manager()
@ -726,7 +726,7 @@ Reference of objects involved in hooks
:undoc-members: :undoc-members:
:show-inheritance: :show-inheritance:
.. autoclass:: _pytest.vendored_packages.pluggy.PluginManager() .. autoclass:: _pytest._pluggy.PluginManager()
:members: :members:
.. currentmodule:: _pytest.pytester .. currentmodule:: _pytest.pytester