In [1] I read:

> If the target list is a comma-separated list of targets, or a single target in square brackets

This come from https://bugs.python.org/issue23275 (patch is [2]).

I suspect there's a missing case "list of targets in square brackets" (and to be pedantic "list of targets in parenthesis").

The specialized documentation about single-valued targets in sequence-like construction come from this difference:

    >>> (a) = 42
    >>> a
    42

    >>> [a] = [42]
    >>> a
    42


which is correctly described the line before:

> If the target list is a single target in parentheses: The object is assigned to that target.

So the correct way to state it may be:

> Else the object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

The `Else`, coupled with the existing "Assignment of an object to a target list, optionally enclosed in parentheses or square brackets" covers properly the cases:

- Multiple target separated by comas (already covered)
- Multiple target enclosed by parenthesis and brackets (not covered)
- Single target enclosed by angle brackets (already covered)


[1]: https://docs.python.org/3.7/reference/simple_stmts.html#assignment-statements
[2]: https://bugs.python.org/file42878/issue23275_v4.diff

I think I intended the third option to include all comma-separated lists, including:

a, b, c = x  # No brackets
(a, b, c) = x  # Round brackets
[a, b, c] = x  # Square brackets
a, = x  # Single target with comma

Perhaps something like this would be clearer:

* If the target list is
    * a comma-separated list of targets, with or without brackets, or
    * a single target with a trailing comma, with or without brackets, or
    * a single target in square brackets,
  the object must be . . .

The empty target list case could also be merged. Then the only differentiation is between a single target (no comma, optional round brackets) and iterable unpacking.

Agree, the empty list could be merged, the only special-case is the "single item in parenthesis", as always.

I'm still exploring the path to simplicity over explicitly listing everything (but in the reference, explicitly listing could be what we need):

    Assignment of an object to a target list, optionally enclosed in parentheses or square brackets, is recursively defined as follows.

        If the target list is a single target in parentheses: The object is assigned to that target.
        Else the object must be an iterable with the same number of items as there are targets in the target list, and the items are assigned, from left to right, to the corresponding targets.

What do you think? Should we go full-explicit, with trailing comas and everything?

I think it is okay to leave out the options for the unpacking case. But I think it is worth clarifying that the single-target case also applies without parentheses, but that it doesn’t apply if there is a trailing comma. So:

‘‘‘
If the target list is a single target with no trailing comma, optionally in parentheses, the object is assigned to that target.

Else the object must be an iterable . . .
’’’

I think that the fact that `(a) = 42` is accepted is rather an implementation detail, and the consequence of limitations of the grammar parser. It accepts arbitrary expression at the left hand side of assignment. After transforming CST to AST unsuitable targets are rejected, but information about grouping parenthesis is lost at this stage.

This can be fixed if check the left hand side node before converting to AST.

I would like to see this fixed.

On Fri, Nov 9, 2018 at 4:27 AM Serhiy Storchaka <report@bugs.python.org>
wrote:

>
> Serhiy Storchaka <storchaka+cpython@gmail.com> added the comment:
>
> I think that the fact that `(a) = 42` is accepted is rather an
> implementation detail, and the consequence of limitations of the grammar
> parser. It accepts arbitrary expression at the left hand side of
> assignment. After transforming CST to AST unsuitable targets are rejected,
> but information about grouping parenthesis is lost at this stage.
>
> This can be fixed if check the left hand side node before converting to
> AST.
>
> ----------
> nosy: +gvanrossum, serhiy.storchaka
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33878>
> _______________________________________
>
-- 
--Guido (mobile)

New changeset 082875dcd6d482558e5f1da97a1c801d60b3ed5b by Julien Palard in branch 'master':
bpo-33878: Doc: Fix missing case by simplifying. (GH-7762)
https://github.com/python/cpython/commit/082875dcd6d482558e5f1da97a1c801d60b3ed5b

New changeset aa493b5c18463ab45c087564e287643606f004ca by Julien Palard (Miss Islington (bot)) in branch '3.7':
bpo-33878: Doc: Fix missing case by simplifying. (GH-7762)
https://github.com/python/cpython/commit/aa493b5c18463ab45c087564e287643606f004ca

New changeset d0ebbf4895439233c8398dbdd0456d07132b2a6f by Julien Palard (Miss Islington (bot)) in branch '3.6':
bpo-33878: Doc: Fix missing case by simplifying. (GH-7762)
https://github.com/python/cpython/commit/d0ebbf4895439233c8398dbdd0456d07132b2a6f