Conversation
bluetech
approved these changes
May 9, 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 #14443 as merged into main (a481f26).
Closes #14442
This fixes a pytest 9 regression where
--strict-markersand--strict-configwere ignored when configured throughaddoptsaddoptsis parsed after the initial config discovery step, so theOverrideIniActioncompatibility path updated the parsed argparse namespace,but the generated ini overrides were not applied back into
_inicfgAs a result, later
getini()calls still saw the default values forstrict_markersandstrict_configThis change applies parsed ini overrides after parsing the full argument list
including
addopts, and clears the ini cache so latergetini()calls use theupdated values
Added regression coverage for:
--strict-configfromaddopts--strict-markersfromaddoptsTested with: