-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
Fix typo in TypeVar docstring #8142
Conversation
"can be used do declare" → "can be used to declare"
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. When your account is ready, please add a comment in this pull request Thanks again for your contribution, we look forward to reviewing it! |
@ilevkivskyi: Please replace |
Thanks @jdferreira for the PR, and @ilevkivskyi for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
GH-8157 is a backport of this pull request to the 3.7 branch. |
"can be used do declare" → "can be used to declare" (cherry picked from commit 86bfed3) Co-authored-by: João D. Ferreira <jotomicron@gmail.com>
Sorry, @jdferreira and @ilevkivskyi, I could not cleanly backport this to |
"can be used do declare" → "can be used to declare" (cherry picked from commit 86bfed3) Co-authored-by: João D. Ferreira <jotomicron@gmail.com>
Is backport to 3.6 still needed? |
It's minor enough that I wouldn't bother with a backport. |
I agree. |
In that case I'll remove the needs backport label. |
Fix a typo in the docstring of typing.TypeVar