Merge pull request #909 from flub/assertdoc
Update docs to represent reality
This commit is contained in:
commit
c605cf92f9
|
@ -228,9 +228,7 @@ Reporting details about a failing assertion is achieved either by rewriting
|
||||||
assert statements before they are run or re-evaluating the assert expression and
|
assert statements before they are run or re-evaluating the assert expression and
|
||||||
recording the intermediate values. Which technique is used depends on the
|
recording the intermediate values. Which technique is used depends on the
|
||||||
location of the assert, ``pytest`` configuration, and Python version being used
|
location of the assert, ``pytest`` configuration, and Python version being used
|
||||||
to run ``pytest``. Note that for assert statements with a manually provided
|
to run ``pytest``.
|
||||||
message, i.e. ``assert expr, message``, no assertion introspection takes place
|
|
||||||
and the manually provided message will be rendered in tracebacks.
|
|
||||||
|
|
||||||
By default, if the Python version is greater than or equal to 2.6, ``pytest``
|
By default, if the Python version is greater than or equal to 2.6, ``pytest``
|
||||||
rewrites assert statements in test modules. Rewritten assert statements put
|
rewrites assert statements in test modules. Rewritten assert statements put
|
||||||
|
|
Loading…
Reference in New Issue