doc: fix test with link to `python_files` (#6741)
Follow-up to b09762d
(#6705).
Ref: https://github.com/pytest-dev/pytest/pull/6705#discussion_r379819573
This commit is contained in:
parent
bc976dca3b
commit
d18c75baa3
|
@ -179,12 +179,12 @@ assertion failures. This is provided by "assertion rewriting" which
|
||||||
modifies the parsed AST before it gets compiled to bytecode. This is
|
modifies the parsed AST before it gets compiled to bytecode. This is
|
||||||
done via a :pep:`302` import hook which gets installed early on when
|
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
|
from what you will run in production, this hook only rewrites test modules
|
||||||
themselves (as defined by the :confval:`python_files` configuration option)
|
themselves (as defined by the :confval:`python_files` configuration option),
|
||||||
themselves as well as any modules which are part of plugins. Any
|
and any modules which are part of plugins.
|
||||||
other imported module will not be rewritten and normal assertion
|
Any other imported module will not be rewritten and normal assertion behaviour
|
||||||
behaviour will happen.
|
will happen.
|
||||||
|
|
||||||
If you have assertion helpers in other modules where you would need
|
If you have assertion helpers in other modules where you would need
|
||||||
assertion rewriting to be enabled you need to ask ``pytest``
|
assertion rewriting to be enabled you need to ask ``pytest``
|
||||||
|
|
Loading…
Reference in New Issue