Follow task tree discipline #89
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Apparently
contextvarsare copied to new tasks at a (to me) from a surprising source: the context of the task that callsstart/start_soonrather than the context that the nursery was opened. See python-trio/trio#1523.The test included in this PR passes if run on Trio from
TreeVarPR except for the part of a task beforetask_status.startedis called... but this seems like a design preference rather than a real barrier.Now the question is: do I urge for the TreeVars to be merged into Trio and constrain requirements to the next release, or do I make myself a
cancel_statuslookalike?