[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- pull_requests: +13679 pull_request: https://github.com/python/cpython/pull/13794 ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Pablo Galindo Salgado added the comment: New changeset 8565f6b6db0fa9f65449b532a5056a98bad3dc37 by Pablo Galindo in branch 'master': bpo-35814: Allow unpacking in r.h.s of annotated assignment expressions (GH-13760)

[issue35814] Syntax quirk with variable annotations

Change by Pablo Galindo Salgado : -- pull_requests: +13645 pull_request: https://github.com/python/cpython/pull/13760 ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- pull_requests: +13638 pull_request: https://github.com/python/cpython/pull/13757 ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Guido van Rossum added the comment: > Is PEP the best place for such updates? Maybe we can add a `versionchanged` > note in > https://docs.python.org/3/reference/simple_stmts.html#annotated-assignment-statements > instead? We should definitely update the docs, with `versionchanged`. But

[issue35814] Syntax quirk with variable annotations

Ivan Levkivskyi added the comment: Is PEP the best place for such updates? Maybe we can add a `versionchanged` note in https://docs.python.org/3/reference/simple_stmts.html#annotated-assignment-statements instead? -- ___ Python tracker

[issue35814] Syntax quirk with variable annotations

Guido van Rossum added the comment: (With a comment indicating that the second is only accepted in Python 3.8 and later.) -- ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Guido van Rossum added the comment: I think PEP 526 does not clarify the intention here. Perhaps we could add a specific example? It currently shows: t: Tuple[int, ...] = (1, 2, 3) We could just add this there: t: Tuple[int, ...] = 1, 2, 3 --

[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 -Python 3.7 ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Ivan Levkivskyi added the comment: New changeset 62c35a8a8ff5854ed470b1c16a7a14f3bb80368c by Ivan Levkivskyi in branch 'master': bpo-35814: Allow same r.h.s. in annotated assignments as in normal ones (GH-11667)

[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- keywords: +patch, patch pull_requests: +11473, 11474 stage: -> patch review ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- keywords: +patch, patch, patch pull_requests: +11473, 11474, 11475 stage: -> patch review ___ Python tracker ___

[issue35814] Syntax quirk with variable annotations

Change by Ivan Levkivskyi : -- keywords: +patch pull_requests: +11473 stage: -> patch review ___ Python tracker ___ ___

[issue35814] Syntax quirk with variable annotations

Ivan Levkivskyi added the comment: Good catch! I think it was just overlooked rather than a conscious decision (unlike the left hand side, that generated lots of debates) I will make a PR to allow everything that is allowed on r.h.s. of a normal assignment. --

[issue35814] Syntax quirk with variable annotations

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum, levkivskyi ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue35814] Syntax quirk with variable annotations

New submission from Raymond Hettinger : Am not sure how much we care about this, but parenthesis around tuples stops being optional when there is a variable annotation. >>> from typing import Tuple >>> t = 10, 'hello' # Parens not normally required >>> t: Tuple[int, str]