<div class="gmail_quote">On Fri, Jan 20, 2012 at 11:51 AM, Donald Stufft <span dir="ltr"><<a href="mailto:donald.stufft@gmail.com">donald.stufft@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
<div></div>
<p style="color:#a0a0a8">On Friday, January 20, 2012 at 2:36 PM, Tres Seaver wrote:</p><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px"><span><div>
<div><div>On 01/20/2012 02:04 PM, Donald Stufft wrote:</div><blockquote type="cite"><div><div>Even if a MemoryException is raised I believe that is still a </div><div>fundamental change in the documented contract of dictionary API.</div>
</div></blockquote><div>How so? Dictionary inserts can *already* raise that error.</div></div></div></span></blockquote></div><div>Because it's raising it for a fundamentally different thing. "You have plenty of memory, but we decided to add an arbitrary limit that has nothing to do with memory and pretend you are out of memory anyways".</div>
</blockquote><div><br>Actually due to fragmentation that can already happen.<br clear="all"></div></div><br>-- <br>--Guido van Rossum (<a href="http://python.org/~guido">python.org/~guido</a>)<br>