never awaited).
(Contributed by Arthur Tacca and Jason Zhang in :gh:`115957`.)
+* The function and methods named ``create_task`` have received a new
+ ``**kwargs`` argument that is passed through to the task constructor.
+ This change was accidentally added in 3.13.3,
+ and broke the API contract for custom task factories.
+ Several third-party task factories implemented workarounds for this.
+ In 3.13.4 and later releases the old factory contract is honored
+ once again (until 3.14).
+ To keep the workarounds working, the extra ``**kwargs`` argument still
+ allows passing additional keyword arguments to :class:`~asyncio.Task`
+ and to custom task factories.
+
+ This affects the following function and methods:
+ :meth:`asyncio.create_task`,
+ :meth:`asyncio.loop.create_task`,
+ :meth:`asyncio.TaskGroup.create_task`.
+ (Contributed by Thomas Grainger in :gh:`128307`.)
base64
------
(Contributed by Semyon Moroz in :gh:`133367`.)
+asyncio
+-------
+
+* The function and methods named :func:`!create_task` now take an arbitrary
+ list of keyword arguments. All keyword arguments are passed to the
+ :class:`~asyncio.Task` constructor or the custom task factory.
+ (See :meth:`~asyncio.loop.set_task_factory` for details.)
+ The ``name`` and ``context`` keyword arguments are no longer special;
+ the name should now be set using the ``name`` keyword argument of the factory,
+ and ``context`` may be ``None``.
+
+ This affects the following function and methods:
+ :meth:`asyncio.create_task`,
+ :meth:`asyncio.loop.create_task`,
+ :meth:`asyncio.TaskGroup.create_task`.
+ (Contributed by Thomas Grainger in :gh:`128307`.)
+
+
bdb
---