
i\c           @` s  d  Z  d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d Z	 d	 Z
 e d
  Z d Z e d  Z e d  Z e d  Z e d  Z e d  Z d Z e d  Z e d  Z e d  Z e e d  Z e e d  Z d S(   s  
This module contains deprecation messages and bits of code used elsewhere in the codebase
that is planned to be removed in the next pytest release.

Keeping it in a central location makes it easy to track what is deprecated and should
be removed when the time comes.

All constants defined in this module should be either PytestWarning instances or UnformattedWarning
in case of warnings which need to format their messages.
i    (   t   absolute_import(   t   division(   t   print_function(   t   PytestDeprecationWarning(   t   RemovedInPytest4Warning(   t   UnformattedWarnings?   yield tests were removed in pytest 4.0 - {name} will be ignoredsf  Fixture "{name}" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.sT   'request' is a reserved name for fixtures and will raise an error in future versionss]   [pytest] section in {filename} files is no longer supported, change to [tool:pytest] instead.s2   getfuncargvalue is deprecated, use getfixturevalues   The 'message' parameter is deprecated.
(did you mean to use `match='some regex'` to check the exception message?)
Please comment on https://github.com/pytest-dev/pytest/issues/3974 if you have concerns about removal of this parameter.s   --result-log is deprecated and scheduled for removal in pytest 5.0.
See https://docs.pytest.org/en/latest/deprecations.html#result-log-result-log for more information.s   raises(..., 'code(as_a_string)') is deprecated, use the context manager form or use `exec()` directly

See https://docs.pytest.org/en/latest/deprecations.html#raises-warns-execs   warns(..., 'code(as_a_string)') is deprecated, use the context manager form or use `exec()` directly.

See https://docs.pytest.org/en/latest/deprecations.html#raises-warns-execsX  Defining 'pytest_plugins' in a non-top-level conftest is no longer supported because it affects the entire directory tree in a non-explicit way.
  {}
Please move it to a top level conftest file at the rootdir:
  {}
For more information, visit:
  https://docs.pytest.org/en/latest/deprecations.html#pytest-plugins-in-non-top-level-conftest-filess   the `pytest.config` global is deprecated.  Please use `request.config` or `pytest_configure` (if you're a pytest plugin) instead.sk   pytest/tmpdir_factory.ensuretemp is deprecated, 
please use the tmp_path fixture or tmp_path_factory.mktemps|   pytest_logwarning is deprecated, no longer being called, and will be removed soon
please use pytest_warning_captured insteadsd   pytest.warns() got unexpected keyword arguments: {args!r}.
This will be an error in future versions.sd   pytest.param() got unexpected keyword arguments: {args!r}.
This will be an error in future versions.N(   t   __doc__t
   __future__R    R   R   t   _pytest.warning_typesR   R   R   t   YIELD_TESTSt   FIXTURE_FUNCTION_CALLt   FIXTURE_NAMED_REQUESTt   CFG_PYTEST_SECTIONt   GETFUNCARGVALUEt   RAISES_MESSAGE_PARAMETERt
   RESULT_LOGt   RAISES_EXECt
   WARNS_EXECt*   PYTEST_PLUGINS_FROM_NON_TOP_LEVEL_CONFTESTt   PYTEST_CONFIG_GLOBALt   PYTEST_ENSURETEMPt   PYTEST_LOGWARNINGt   PYTEST_WARNS_UNKNOWN_KWARGSt   PYTEST_PARAM_UNKNOWN_KWARGS(    (    (    s1   lib/python2.7/site-packages/_pytest/deprecated.pyt   <module>   sD   											