[PR #14113/6d0aff14 backport][9.0.x] Docs: clarify -p vs PYTEST_PLUGINS plugin loading#14117
Merged
nicoddemus merged 1 commit into9.0.xfrom Jan 17, 2026
Conversation
nicoddemus
approved these changes
Jan 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a backport of PR #14113 as merged into main (6d0aff1).
Summary
This PR clarifies the difference between
-pandPYTEST_PLUGINSin the plugin documentation and fixes an incorrect command example.Details
pytest --disable-plugin-autoload -p NAME,NAME2→ replaced with the correct repeated form
-p NAME -p NAME2-pearly-loads (or disables) a plugin by name or entry point for a single invocationPYTEST_PLUGINSloads plugin modules during startup, commonly used when testing pluginscloses #13388
Changelog: not needed (documentation-only change).