René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Audit asyncio thread safety ","articleBody":"The following functions needs to be made thread safe and atomic for free-threading for both pure python and C implementation:\r\n\r\n- [x] `asyncio._enter_task`\r\n- [x] `asyncio._leave_task` \r\n- [x] `asyncio._register_task`\r\n- [x] `asyncio._unregister_task`\r\n- [x] `asyncio._swap_current_task` \r\n- [x] `asyncio.current_task` \r\n- [x] `asyncio.all_tasks` \r\n\r\nNote that some of these were made thread safe in C impl https://github.com/python/cpython/issues/120974\r\n\r\nThe following classes needs to be thread safe for free-threading in C implementation: \r\n- [x] `asyncio.Task`\r\n- [x] `asyncio.Future`\r\n\r\nBoth of these classes are documented to be not thread safe but currently calling methods on these classes from multiple threads can crash the interpreter. The pure python implementation cannot crash the interpreter when called from multiple threads so changes are only needed for C implementation.  Before making these thread safe in C I would gather some numbers for how much a difference the C implementation makes in free-threading and if it isn't much we can just disable the C extension for free-threading. \r\n\r\ncc @colesbury \r\n\r\n\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-128147\n* gh-128256\n* gh-128480\n* gh-128541\n* gh-128869\n* gh-128885\n* gh-129267\n* gh-129942\n* gh-129943\n* gh-129995\n* gh-130518\n* gh-131106\n* gh-131397\n* gh-131399\n* gh-131797\n* gh-134362\n* gh-134324\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/kumaraditya303","@type":"Person","name":"kumaraditya303"},"datePublished":"2024-12-16T18:29:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":12},"url":"https://github.com/128002/cpython/issues/128002"}