➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients Camion, eric.smith, r.david.murray, rhettinger, serhiy.storchaka, steven.daprano
Date 2017-12-10.21:15:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512940555.89.0.213398074469.issue32259@psf.upfronthosting.co.za>
In-reply-to
Content 
> How about "[TYPE] object is not iterable/unpackable"

I just grepped the docs, and the term 'unpackable' does not appear anywhere in them.  I don't think this would be an improvement.

As for the earlier suggestion of adding "expected tuple" does not work, because it is not a tuple being expected, it is an iterable, and saying "expected iterable" would be redundant with saying "is not iterable".

What about "TypeError: expected iterable but found <type>"?  That's parallel to some other type error messages we already generate.  Would that be any clearer?  (I'm not sure it would be, it says the same thing.)
History
Date User Action Args
2017-12-10 21:15:55r.david.murraysetrecipients: + r.david.murray, rhettinger, eric.smith, steven.daprano, serhiy.storchaka, Camion
2017-12-10 21:15:55r.david.murraysetmessageid: <1512940555.89.0.213398074469.issue32259@psf.upfronthosting.co.za>
2017-12-10 21:15:55r.david.murraylinkissue32259 messages
2017-12-10 21:15:55r.david.murraycreate