➜

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 martin.panter
Recipients DragonFireCK, Samuel BOVÉE, amaury.forgeotdarc, benjamin.peterson, brandjon, dangyogi, daniel.urban, georg.brandl, gpolo, hagen, kcarnold, martin.panter, ncoghlan, pfctdayelise, pitrou, python-dev, r.david.murray, ron_adam, terry.reedy, yselivanov
Date 2016-01-30.11:21:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454152906.75.0.593186961936.issue4806@psf.upfronthosting.co.za>
In-reply-to
Content 
In Python 2, the old-style “instance” objects are making it hard to fix this like in Python 3. And completely removing the custom error message seems a bit drastic for 2.7.

Instead, I propose to just check for a generator type after the TypeError is caught, and don’t bother checking for other kinds of iterables and sequences.
History
Date User Action Args
2016-01-30 11:21:46martin.pantersetrecipients: + martin.panter, georg.brandl, terry.reedy, amaury.forgeotdarc, ncoghlan, pitrou, ron_adam, dangyogi, benjamin.peterson, gpolo, hagen, kcarnold, r.david.murray, daniel.urban, python-dev, pfctdayelise, brandjon, yselivanov, DragonFireCK, Samuel BOVÉE
2016-01-30 11:21:46martin.pantersetmessageid: <1454152906.75.0.593186961936.issue4806@psf.upfronthosting.co.za>
2016-01-30 11:21:46martin.panterlinkissue4806 messages
2016-01-30 11:21:46martin.pantercreate