Fix typo with missing colon in try statement
#26911
Conversation
The `try` statement was missing a colon and therefore was not exemplifying the correct `SyntaxError`.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: @RojerGS This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
iritkatriel
added
needs backport to 3.10
|
Thanks @RogerGs. We can merge a typo fix without you signing the CLA if you don't want to, but ideally you should sign it so that you can make more substantial contributions. |
|
@iritkatriel I made the PR and signed the CLA during the weekend, so it took some time to process. This was a light first PR. Let's see if I can make more significant contributions 😄 |
|
Thanks @RojerGS for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
|
GH-26940 is a backport of this pull request to the 3.10 branch. |
|
@RojerGS Welcome to CPython! |
The `try` statement was missing a colon and therefore was not exemplifying the correct `SyntaxError`. (cherry picked from commit dcb1cae) Co-authored-by: Rodrigo Girão Serrão <[email protected]>
The `try` statement was missing a colon and therefore was not exemplifying the correct `SyntaxError`. (cherry picked from commit dcb1cae) Co-authored-by: Rodrigo Girão Serrão <[email protected]>
The
trystatement was missing a colon and therefore was not exemplifying the correctSyntaxError.As per the Python Developer's Guide, 6.3 Proofreading, this PR is not linked to any bpo issue.