docs: correct futures example comments - #249
Open
nightcityblade wants to merge 1 commit into
Open
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Author
|
CI note: the failures are unrelated to this notebook-comment-only diff. The build-and-deploy and update-dependencies jobs are blocked by deprecated actions/cache v2 usage; pre-commit failed while GitHub cache services were unavailable; and the repo2docker build cannot solve the existing pinned Binder environment. Recent main-branch runs show the same workflow failures. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #247
Correct the inline descriptions for the
doubleandaddfutures so they match the functions submitted in the example.Validation:
futures.ipynbwithnbformatpre-commit run --files futures.ipynb