chore(deps): update dependency trio to v0.29.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
trio (changelog)	==0.27.0 -> ==0.29.0

---

Release Notes

python-trio/trio (trio)

v0.29.0

Compare Source

Full Changelog: python-trio/trio@v0.28.0...v0.29.0

Features

• Add trio.lowlevel.in_trio_run and trio.lowlevel.in_trio_task and document the semantics (and differences) thereof. (https://github.com/python-trio/trio/issues/2757)
• 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. (https://github.com/python-trio/trio/issues/3145)

Bugfixes

• Clear Trio's cache of worker threads upon os.fork. (https://github.com/python-trio/trio/issues/2764)

Miscellaneous internal changes

• Stop using ctypes to mutate tracebacks for strict_exception_groups=False's exception collapsing. (https://github.com/python-trio/trio/issues/405)

• Fixed spelling error in Windows error code enum for ERROR_INVALID_PARAMETER. (https://github.com/python-trio/trio/issues/3166)

• Publicly re-export __version__ for type checking purposes. (https://github.com/python-trio/trio/issues/3186)

• The typing of 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 trio.to_thread.run_sync, trio.from_thread.run and trio.from_thread.run_sync has been improved and should reflect the underlying function being run. (https://github.com/python-trio/trio/issues/3201)

v0.28.0

Compare Source

Full Changelog: python-trio/trio@v0.27.0...v0.28.0

Bugfixes

• :func:inspect.iscoroutinefunction and the like now give correct answers when
  called on KI-protected functionhttps://github.com/python-trio/trio/issues/26702670)

• Rework KeyboardInterrupt protection to track code objects, rather than frames,
  as protected or not. The new implementation no longer needs to access
  frame.f_locals dictionaries, so it won't artificially extend the lifetime of
  local variables. Since KeyboardInterrupt protection is now imposed statically
  (when a protected function is defined) rather than each time the function runs,
  its previously-noticeable performance overhead should now be near zero.
  The lack of a call-time wrapper has some other benefits as well:

  • :func:inspect.iscoroutinefunction and the like now give correct answers when
    called on KI-protected functions.

  • Calling a synchronous KI-protected function no longer pushes an additional stack
    frame, so tracebacks are clearer.

  • A synchronous KI-protected function invoked from C code (such as a weakref
    finalizer) is now guaranteed to start executing; previously there would be a brief
    window in which KeyboardInterrupt could be raised before the protection was
    established.

  One minor drawback of the new approach is that multiple instances of the same
  closure share a single KeyboardInterrupt protection state (because they share a
  single code object). That means that if you apply
  trio.lowlevel.enable_ki_protection to some of them
  and not others, you won't get the protection semantics you asked for. See the
  documentation of trio.lowlevel.enable_ki_protection
  for more details and a workarounhttps://github.com/python-trio/trio/issues/31083108)

• Rework foreign async generator finalization to track async generator
  ids rather than mutating ag_frame.f_locals. This fixes an issue
  with the previous implementation: locals' lifetimes will no longer be
  extended by materialization in the ag_frame.f_locals dictionary that
  the previous finalization dispatcher logic needed to access to do its worhttps://github.com/python-trio/trio/issues/31123112)

• Ensure that Pyright recognizes our underscore prefixed attributes for attrs classes. (https://github.com/python-trio/trio/issues/3114)

• Fix trio.testing.RaisesGroup's typing. (https://github.com/python-trio/trio/issues/3141)

Improved documentation

• Improve error message when run after gevent's monkey patching. (https://github.com/python-trio/trio/issues/3087)
• Document that trio.sleep_forever is guaranteed to raise an exception now. (https://github.com/python-trio/trio/issues/3113)

Removals without deprecations

• Remove workaround for OpenSSL 1.1.1 DTLS ClientHello bug. (https://github.com/python-trio/trio/issues/3097)
• Drop support for Python 3.8. (https://github.com/python-trio/trio/issues/3104) (https://github.com/python-trio/trio/issues/3106)

Miscellaneous internal changes

• Switch to using PEP570 for positional-only arguments for trio.socket.SocketType's methods. (https://github.com/python-trio/trio/issues/3094)
• Improve type annotations in several places by removing Any usage. (https://github.com/python-trio/trio/issues/3121)
• Get and enforce 100% coverage (https://github.com/python-trio/trio/issues/3159)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	eddb6c8
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/67af296938977b000841539e
😎 Deploy Preview	https://deploy-preview-2167--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.