bpo-31647: fix typo in blurb's bpo number #7964
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
Member
|
Thanks for the PR. This will fix the master branch but it should not be backported directly to 3.7 and 3.6 as their NEWS files have already been finalized for 3.7.0 and 3.6.6. I will manually fix the entries for them once the releases are complete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
I entered a wrong bpo number when preparing the previous PR that fixed bpo-31647. As a result the blurb entry had the wrong number, and the changelog in built documentation links to the wrong issue. This PR renames the blurb entry to the correct number.
https://bugs.python.org/issue31647