Jan Kaliszewski added the comment:
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.
----------
nosy: +zuo
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue18533>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
