Clarify import vs. distribution packages in Using importlib_metadata docs #399
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.
As requested on the Python Discourse, addresses #398 (import vs. distribution packages not being clear) by:
package_distributions()
function to map between themAdditionally, this incorporates a couple required/directly related changes:
Fix #398
Reviewer notes:
Footnotes
I'm not 100% sure myself about the disambiguations in the highly technical
Extending the search algorithm
Explanation—please check to confirm I've gotten them correct. ↩So readers don't have to go hunting through other sections to find them, if they do so at all ↩
If this needs to go in your skeleton, I can submit a PR there, drop that commit here and rebase accordingly once that is updated. Also, I was confused by some were written as dict literals, and some were added with
dict.update
, with no obvious or stated reason—I though it might have to do with the former being from your skeleton and the latter being local, but your skeleton looks identical, so I'm not sure what's going on or where packaging.python.org. Please advise and I'll be happy to add it in whichever manner is appropriate. ↩If required, I can pull this out to a separate followup PR, though it is small enough I just added it here to avoid extra overhead on both our parts. ↩