Clarify import package terminology - #810
Merged
takluyver merged 1 commit intoSep 5, 2026
Merged
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
2 participants
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
Clarify that Flit's top-level packages and automatically included subpackages are both import packages.
Why
The existing wording could be read as mixing distribution-package and import-package terminology. The updated bullet uses the maintainer-provided
djangohierarchy to make the distinction explicit.Fixes #618
Testing
doc/rationale.rstgit diff --checkThe repository-wide linkcheck also reached an unrelated existing HTTP 403 for
docutils.sourceforge.ioindoc/pyproject_toml.rst; the edited page's links all passed.