[issue16916] The Extended Iterable Unpacking (PEP-3132) for byte strings doesn't match the specification

2013-01-11 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16916 ___ ___ Python-bugs-list

[issue16916] The Extended Iterable Unpacking (PEP-3132) for byte strings doesn't match the specification

2013-01-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset a0077c1d201d by Georg Brandl in branch 'default': Closes #16916: clarify slicing equivalent to extended unpacking example: the latter always creates a list. http://hg.python.org/peps/rev/a0077c1d201d -- nosy: +python-dev resolution: -

[issue16916] The Extended Iterable Unpacking (PEP-3132) for byte strings doesn't match the specification

2013-01-11 Thread Georg Brandl
Georg Brandl added the comment: Thanks for the report. This statement was actually false for almost all sequence types, except for those whose slicing returns a list. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org

[issue16916] The Extended Iterable Unpacking (PEP-3132) for byte strings doesn't match the specification

2013-01-10 Thread Marco Buttu
New submission from Marco Buttu: The PEP 3132 said: ... if seq is a slicable sequence, all the following assignments are equivalent if seq has at least three elements: a, b, c = seq[0], seq[1:-1], seq[-1] a, *b, c = seq [a, *b, c] = seq But this doesn't happen for byte strings: seq =