Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3rd alpha release.
Also tossed in 3.10 to CI let's see if that works 😂
Notes for trio montly, ping @Fuyukai:
tractor
saw its 4th alpha release with some interesting improvements in the core cross-actor cancellation mechanics as well as the start of a public expose of what were our internaltrio
helper API goodies and we officially now have optionalmsgspec
support!The quick feature summary:
trio
/subprocess
spawner by default which means windows users now get multi-core debugger support out of the box.msgspec
lib usage for those who want a faster and typed codec alternative tomsgpack-python
.tractor.trionics
which is where we'll be stashing all our "higher level"trio
related helper APIs going forward. For example checkout our newgather_contexts
concurrent context manager enter-er (kinda like a concurrent version ofasyncio.gather()
but for context manager instances).requests immediately instead of scheduling them as is done for rpc-task
requests. Previously cancel requests were actually scheduled as rpc requests but this has changed to instead invoke a synchronous style cancellation which resulted in a massive reduction in teardown race conditions particularly in our anti-zombie-process machinery and it's interaction with the debugger system.