asyncio has underscored names in its `__all__`

[JelleZijlstra]

Bug report

Bug description:

asyncio has several names in its __all__ that start with an underscore.

Python 3.15.0a0 (heads/assignannos:9081715ff82, May 25 2025, 08:33:06) [Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import asyncio
>>> [x for x in asyncio.__all__ if x.startswith("_")]
['_AbstractEventLoopPolicy', '_get_event_loop_policy', '_set_event_loop_policy', '_set_running_loop', '_get_running_loop', '_register_task', '_unregister_task', '_enter_task', '_leave_task', '_DefaultEventLoopPolicy']

That feels wrong: __all__ indicates the public names in the module, and names that start with an underscore are not meant to be public.

In Python 3.13 there were fewer:

['_set_running_loop', '_get_running_loop', '_register_task', '_unregister_task', '_enter_task', '_leave_task']

I propose we remove the new additions in 3.14 in both the 3.14 and main branches, and remove the remaining underscored names in 3.15.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-134657: Remove newly added private names from asyncio.__all__ #134665

[picnixz]

IIRC, the private names were added when the policy system was being deprecated cc @kumaraditya303 (I don't know if it was meant for bc)

[JelleZijlstra]

Yes, in #128218. I don't see how re-adding them to __all__ under a different name helps backwards compatibility for anyone; it just makes it slightly easier for people to use the private names.

[kumaraditya303]

It wasn't for backwards compatibility, it was to reduce the diff when deprecating it, these underscored functions and classes will be removed in 3.16 anyways so making a lot of name changes didn't seem worth it.