why python not crash in this case?
<p>For the example in this page:
<a href="https://wiki.python.org/moin/CrashingPython#Exhausting_Resources" rel="nofollow">https://wiki.python.org/moin/CrashingPython#Exhausting_Resources</a>
Why the case can't be reproduced in my python 2.7 
Why it can make python crash?</p>

<pre><code>$ python
Python 2.4.2 (#2, Sep 30 2005, 21:19:01) 
[GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu8)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
&gt;&gt;&gt; f = lambda: None
&gt;&gt;&gt; for i in xrange(1000000):
...     f = f.__call__
... 
&gt;&gt;&gt; del f
Segmentation fault
</code></pre>

<p>This was simply a bug, see <a href="http://bugs.python.org/issue532646" rel="nofollow">issue #532646</a>.</p>

<p>All software has bugs, and the Python project is no exception. It can't be reproduced in 2.7 because the bug was found and fixed.</p>

<p>Specifically, the page you found documents various such crashing bugs, and it states so <em>at the top</em>:</p>

<blockquote>
  <p>While a lot of effort has gone into making it difficult or impossible to crash the Python interpreter in normal usage, there are lots fairly easy ways to crash the interpreter. The BDFL pronounced recently on the python-dev mailing list:</p>
  
  <blockquote>
    <p>I'm not saying it's uncrashable. I'm saying that if you crash it, it's a bug unless proven harebrained.</p>
  </blockquote>
</blockquote>

<p>Any known, still outstanding bugs are added to the <a href="https://hg.python.org/cpython/file/2.7/Lib/test/crashers" rel="nofollow">crashers test suite</a>. If you follow back the history on those tests, you'll be able to find more crashers and the versions of Python they apply to. Most require obscure setups like the one in your question.</p>

python