René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"threading Thread.join should call the OS join API","articleBody":"# Feature or enhancement\n\n### Proposal:\n\n`threading.Thread.join()` only waits for the CPython internals to wash its hands of the underlying thread. It doesn't actually wait for the OS thread itself to exit, which in theory happens rapidly as its final internal code completes quickly - but we have no good wait to determine.\n\nWhy finally do this now?  Now that we're encouraging people to notice and avoid threading existing when `os.fork` is called in 3.12, a use case has come up for deterministically knowing when the thread is done at the OS level so that the code can proceed with `os.fork`.\n\nhttps://github.com/python/cpython/pull/110510 could use this in an atfork before fork handler for example.\n\nPOSIX has pthread_join, we should be able to expose and use via `_thread`.  Windows presumably has an equivalent concept API.\n\n### Has this already been discussed elsewhere?\n\nNo response given\n\n### Links to previous discussion of this feature:\n\n_No response_\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-110848\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/gpshead","@type":"Person","name":"gpshead"},"datePublished":"2023-10-13T13:31:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/110829/cpython/issues/110829"}