1.2 KiB
Prompt
Build on the human’s cancellation-reason/context-status prototype, keeping the minimum Trio version bump separate from context changes.
Response summary
Require Trio >=0.34.0, the installed version whose object-valued cancellation-reason behavior was inspected and exercised. Update the lock with uv lock –upgrade-package trio==0.34.0. The initial offline attempt could not resolve uncached registry metadata; normal resolution updated Trio alone as a package version, also synchronizing an existing py-multibase requirement in lock metadata. No environment was synced.
Files changed
- pyproject.toml: Trio minimum and explanatory dependency comment.
- uv.lock: Trio package metadata and project requirement synchronization.
Human contributions
The human proposed a downstream experiment, explicitly accepted the implementation-dependent nature of non-string reason payloads, and required the dependency bump and context code to be separate commits.
Limit
The minimum selects a verified implementation. It does not turn arbitrary object reasons into a documented stable Trio public contract.