Message269099
The t vs x mixup was introduced by my sloppy backport in Issue 16701. The other problem here is x is generally defined as any arbitrary object, but redefined as an iterable in the footnote. I think we should use t instead, as in the other two slice assignment operations and in Python 3. My commit should have fixed both these problems. |
|
Date |
User |
Action |
Args |
2016-06-23 01:11:07 | martin.panter | set | recipients:
+ martin.panter, docs@python, python-dev, Andrew Cameron |
2016-06-23 01:11:07 | martin.panter | set | messageid: <1466644267.56.0.459041650643.issue27370@psf.upfronthosting.co.za> |
2016-06-23 01:11:07 | martin.panter | link | issue27370 messages |
2016-06-23 01:11:06 | martin.panter | create | |
|