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

doc: link to `python_files` from "Assertion Rewriting" (#6705) 

Ref: https://github.com/pytest-dev/pytest/issues/6377
Ref: https://github.com/blueyed/pytest/pull/145
This commit is contained in:
Daniel Hahler 2020-02-15 00:32:16 +01:00 committed by GitHub
parent 9631b3c166
commit b09762df27
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/en/writing_plugins.rst
View File

@ -181,6 +181,7 @@ done via a :pep:`302` import hook which gets installed early on when
``pytest`` starts up and will perform this rewriting when modules get ``pytest`` starts up and will perform this rewriting when modules get
imported. However since we do not want to test different bytecode imported. However since we do not want to test different bytecode
then you will run in production this hook only rewrites test modules then you will run in production this hook only rewrites test modules
themselves (as defined by the :confval:`python_files` configuration option)
themselves as well as any modules which are part of plugins. Any themselves as well as any modules which are part of plugins. Any
other imported module will not be rewritten and normal assertion other imported module will not be rewritten and normal assertion
behaviour will happen. behaviour will happen.