docs: Clarify difference between PYTEST_PLUGINS and -p option #13840
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a note to the PYTEST_PLUGINS environment variable documentation explaining the difference between PYTEST_PLUGINS and the -p command-line option. This addresses issue #13388 by clarifying that PYTEST_PLUGINS is processed before command-line arguments, making it suitable for always loading plugins, while -p is better for one-time plugin loading or testing.