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 Walter.Woods, barry, dstanek, eric.araujo, hdiogenes, l0nwlf, orsenthil, r.david.murray
Date 2010-08-02.00:37:32
SpamBayes Score 0.00010638098
Marked as misclassified No
Message-id <1280709455.54.0.464478867876.issue8572@psf.upfronthosting.co.za>
In-reply-to
Content
Joining the iterator contents if default is an iterator is an ugly backward compatibility hack.  The default should really be returned unchanged.  But given there is code in the field working around the current bug, I guess we have to retain it.  Of course, it will fail if the iterator contains non-strings...oh well.

Perhaps we could add a deprecation warning when an iterator is used as a default, and in 3.3 stop special casing iterators.

And I agree that only iterators should be special cased, since anything else would currently be failing, and should instead be returned unchanged.
History
Date User Action Args
2010-08-02 00:37:36r.david.murraysetrecipients: + r.david.murray, barry, orsenthil, dstanek, hdiogenes, eric.araujo, l0nwlf, Walter.Woods
2010-08-02 00:37:35r.david.murraysetmessageid: <1280709455.54.0.464478867876.issue8572@psf.upfronthosting.co.za>
2010-08-02 00:37:34r.david.murraylinkissue8572 messages
2010-08-02 00:37:33r.david.murraycreate