docs: explain filesystem tests in frozen applications - #14789
Draft
Lem0nTea2002 wants to merge 1 commit into
Draft
docs: explain filesystem tests in frozen applications#14789Lem0nTea2002 wants to merge 1 commit into
Lem0nTea2002 wants to merge 1 commit into
Conversation
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.
Summary
--add-data.__file__and pass that path topytest.main().Why
--pyargscan resolve importable packages, but pytest still needs filesystem paths when collecting Python test modules. The documentation now makes that boundary explicit and gives frozen applications a supported filesystem-backed layout.Related to #14771.
Validation
uvx tox -e docs -- --show-traceback(256 documentation sources, warnings treated as errors)uvx towncrier build --draft --version 9.2.0git diff --checkAI assistance
OpenAI Codex assisted with drafting the documentation change and running validation. The human contributor reviewed the complete diff and validation results before this draft pull request was opened and takes responsibility for the contribution.