<br><br><div class="gmail_quote">On Sun, Apr 15, 2012 at 6:18 PM, Victor Stinner <span dir="ltr"><<a href="mailto:victor.stinner@gmail.com">victor.stinner@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">> Here is a simplified version of the first draft of the PEP 418. The<br>
> full version can be read online.<br>
> <a href="http://www.python.org/dev/peps/pep-0418/" target="_blank">http://www.python.org/dev/peps/pep-0418/</a><br>
<br>
</div>FYI there is no time.thread_time() function. It would only be<br>
available on Windows and Linux. It does not use seconds but CPU<br>
cycles. No module or program of the Python source code need such<br>
function,</blockquote><div><br></div><div>Just FYI: in MACOSx, you can use thread_info() to get that information. Also you can get that information in Solaris,too. In yappi profiler I use all of these approaches together to have an OS independent thread_times() functionality. Here is the relevant code:<a href="https://bitbucket.org/sumerc/yappi/src/7c7dc11e8728/timing.c">http://bitbucket.org/sumerc/yappi/src/7c7dc11e8728/timing.c</a></div>
<div><br></div><div>I also think that you are right about Python really not have any use case for this functionality, ...</div></div><br clear="all"><div><br></div>-- <br>Sümer Cip<br>