-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename stuff to keep up with new 'checkpoint' nomenclature #157
Comments
Will probably do this right after landing the giant ssl branch of doom. |
Actually, we should probably just deprecate |
njsmith
added a commit
to njsmith/trio
that referenced
this issue
Nov 28, 2017
This was deprecated as part of python-triogh-157 due to lack of use cases, but python-triogh-329 reported a plausible use-case so let's put it back.
njsmith
added a commit
to njsmith/trio
that referenced
this issue
Dec 25, 2017
njsmith
added a commit
to njsmith/trio
that referenced
this issue
Dec 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
assert_yields
→assert_checkpoints
assert_no_yields
→just deprecate without replacementassert_no_checkpoints
yield_briefly
→checkpoint
yield_briefly_no_cancel
→checkpoint_never_cancelled
,schedule_point
,checkpoint_shielded
, ...?checkpoint_ignore_cancelled
?checkpoint_with_cancel_shield
?never_cancelled_checkpoint
?cancel_shielded_checkpoint
yield_if_cancelled
→checkpoint_if_cancelled
?if_cancelled_checkpoint
?Naw, let's make ityield_indefinitely
can stay the same, or maybeblock_indefinitely
,block_task_indefinitely
?yield_indefinitely
→wait_task_rescheduled
, for parallelism with the otherwait
functions.The text was updated successfully, but these errors were encountered: