bpo-46838: Syntax error improvements for function definitions - #31590
Merged
pablogsal merged 3 commits intoMar 22, 2022
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
AlexWaygood
reviewed
Feb 25, 2022
Comment thread
Misc/NEWS.d/next/Core and Builtins/2022-02-25-22-42-30.bpo-46838.RB6kEy.rst
Outdated
…38.RB6kEy.rst Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
Copy link
Copy Markdown
|
It's great that all the points for function defenition have worked out.
|
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
No, I will add those in another commit
I left it uncovered because that's going to be quite rare and I think is not worth the extra rule |
Sorry, something went wrong.
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
Reviewers
5 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.
First round of improvements for function definitions.
https://bugs.python.org/issue46838