A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-May/111723.html below:

[Python-Dev] [Python-checkins] cpython: Close #12028: Make threading._get_ident() public, rename it to

[Python-Dev] [Python-checkins] cpython: Close #12028: Make threading._get_ident() public, rename it to [Python-Dev] [Python-checkins] cpython: Close #12028: Make threading._get_ident() public, rename it toNick Coghlan ncoghlan at gmail.com
Tue May 31 07:44:17 CEST 2011
On Tue, May 31, 2011 at 7:04 AM, victor.stinner
<python-checkins at python.org> wrote:
> +.. function:: get_ident()
> +
> +   Return the 'thread identifier' of the current thread.  This is a nonzero
> +   integer.  Its value has no direct meaning; it is intended as a magic cookie
> +   to be used e.g. to index a dictionary of thread-specific data.  Thread
> +   identifiers may be recycled when a thread exits and another thread is
> +   created.

That's not quite true - the Thread id isn't relinquished until the
Thread object itself is destroyed, rather than when the underlying
thread finishes execution (i.e. the lifecycle of a_thread.ident is the
same as that of id(a_thread)).

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4