Log Message:
py-trio: updated to 0.29.0

Trio 0.29.0 (2025-02-14)

Features

- Add :func:`trio.lowlevel.in_trio_run` and :func:`trio.lowlevel.in_trio_task` \ 
and document the semantics (and differences) thereof. See :ref:`the \ 
documentation <trio_contexts>`.
- If `trio.testing.RaisesGroup` does not get the expected exceptions it now \ 
raises an `AssertionError` with a helpful message, instead of letting the raised \ 
exception/group fall through. The raised exception is available in the \ 
``__context__`` of the `AssertionError` and can be seen in the traceback.

Bugfixes

- Clear Trio's cache of worker threads upon `os.fork`.

Miscellaneous internal changes

- Stop using ctypes to mutate tracebacks for ``strict_exception_groups=False``'s \ 
exception collapsing.
- Fixed spelling error in Windows error code enum for ``ERROR_INVALID_PARAMETER``.
- Publicly re-export ``__version__`` for type checking purposes.
- The typing of :func:`trio.abc.HostnameResolver.getaddrinfo` has been corrected to
  match that of the stdlib `socket.getaddrinfo`, which was updated in mypy 1.15 (via
  a typeshed update) to include the possibility of ``tuple[int, bytes]`` for the
  ``sockaddr`` field of the result. This happens in situations where Python was \ 
compiled
  with ``--disable-ipv6``.

  Additionally, the static typing of :func:`trio.to_thread.run_sync`,
  :func:`trio.from_thread.run` and :func:`trio.from_thread.run_sync` has been
  improved and should reflect the underlying function being run.