experimental-inspect: write nested package stubs into their own directory - #6365
Merged
Merged
Conversation
experimental-inspect: write nested package stubs into their own directory
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.
What was wrong
add_module_stub_filesused a singlemodule_path: &[&str]argument for two different things: the output directory and the list of parent module names. The recursive call passed[...ancestors, parent_name], which is right as parents and wrong as a directory. A package nested inside a package wrote its__init__.pyiunder a directory named after its parent, its own name disappeared from the tree, and its leaf submodules landed one level too shallow.pytestshas no nested package, so nothing in the test suite exercised it.Reproduction
The fix
Split the argument into
directory: &Pathandparents: &[&str]. The directory descends by the submodule's own name;parentsaccumulates module names exactly as before, somodule_stubsandmake_module_path_relativeare unchanged in behaviour.