-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove empty footnote section #30451
Remove empty footnote section #30451
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR is stale because it has been open for 30 days with no activity. |
@encukou Can we get this merged? |
@JelleZijlstra This can be merged. |
Going to merge this into 3.10 and main only because in the 3.9 docs there is a footnote. (cc @gvanrossum) |
Thanks @nedbat for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
GH-31745 is a backport of this pull request to the 3.10 branch. |
(cherry picked from commit 13331a1) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
(cherry picked from commit 13331a1) Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
This change gets overwritten when syncing the changes from importlib_metadata, such as in #31854. I can port the change to importlib_metadata so that doesn't happen, but please be cognizant of making editorial changes to importlib.metadata, importlib.resources, and the docs for importlib.metadata, as they're kept in sync with the backports. If you have any suggestions on how to guide contributors to limit these sorts of edits, please let me know. |
Ported as python/importlib_metadata@467dba53dd48. |
There are no footnotes on this page, so no need for a "Footnotes" header.