<br><br><div><span class="gmail_quote">On 7/8/06, <b class="gmail_sendername">Tim Peters</b> <<a href="mailto:tim.peters@gmail.com">tim.peters@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Back in:<br><br> <a href="http://mail.python.org/pipermail/python-dev/2005-March/051856.html">http://mail.python.org/pipermail/python-dev/2005-March/051856.html</a><br><br>I made a pitch for adding:<br><br> sys._current_frames()
<br><br>to 2.5, which would return a dict mapping each thread's id to that<br>thread's current (Python) frame. As noted there, an extension module<br>exists along these lines that's used at least by the popular Zope<br>DeadlockDebugger product, but it's not possible to do it correctly in
<br>an extension. The latter is why it needs to be in the core (so long<br>as it's in an extension, it risks segfaulting, because the core's<br>internal `head_mutex` lock isn't exposed).<br><br>I forgot about this but was recently reminded. How much opposition
<br>would there be to sneaking this into 2.5b2? It would consist of<br>adding a relatively simple new function, docs, and tests; since it<br>wouldn't _change_ any existing code, it would have a hard time<br>breaking anything that currently works.
</blockquote><div><br>Well, my understanding is that beta is feature freeze, so I am going to say we shouldn't do this. Obviously this can go in day one when 2.6 is started.<br><br>Anyway, this is a true test of how rigid the rules are! Can Neal and Anthony going to say no to Uncle Timmy? =)
<br> <br>-Brett<br></div></div>