Armin Rigo added the comment:
Hi Raymond! Yes, I had the same reaction at first, but then it seemed to be
possible to implement a reasonably good behavior with almost no performance hit.
Plainly undefined behaviors are a mess for other implementations because in
half of the big projects people don't realize they depend on it at some place
--- particularly if the behavior is "mostly sane", as it seems to be right now
for OrderedDict.
For example, I believe the following code to always work:
for key in ordered_dict:
if some_condition:
del ordered_dict[key]
whereas it always raise RuntimeError with regular dicts, which are both ok
choices. But silently not working would be much worse.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19414>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
