Author zuo
Recipients bennorth, terry.reedy, vstinner, zuo
Date 2013-07-22.23:46:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374536780.96.0.530674196979.issue18533@psf.upfronthosting.co.za>
In-reply-to
Content
As I wrote on the list -- IMHO it's still a bug (even though not so painful as segfault) that should also be fixed in 2.7 and 3.2/3.3.  In other cases (such as `d={}; d[42]=d; repr(d)`) Python does its best to avoid an error -- why in this case (`d={}; d[42]=d.<Py2.x:view>values(); repr(d)`) should it raise an exception? IMHO it's an obvious oversight in implementation, not a feature that anybody would expect.
History
Date User Action Args
2013-07-22 23:46:21zuosetrecipients: + zuo, terry.reedy, vstinner, bennorth
2013-07-22 23:46:20zuosetmessageid: <1374536780.96.0.530674196979.issue18533@psf.upfronthosting.co.za>
2013-07-22 23:46:20zuolinkissue18533 messages
2013-07-22 23:46:20zuocreate