-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
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 references to methods
attr
#26806
Fix references to methods
attr
#26806
Conversation
Doc/library/crypt.rst
Outdated
@@ -93,7 +93,7 @@ The :mod:`crypt` module defines the following functions: | |||
may be available on all platforms), or a full encrypted password | |||
including salt, as returned by this function. If *salt* is not | |||
provided, the strongest method will be used (as returned by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If methods
is not a function, do we need the wording as returned by
? We usually use return for results of functions and methods. Am assuming due diligence, that methods
is actually an attribute, not a method, therefore someone else can confirm on this.
Yep, methods is just a simple python list in fact, I will update the
wording..
…On Tue, Jun 22, 2021 at 8:58 AM Joannah Nanjekye ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In Doc/library/crypt.rst
<#26806 (comment)>:
> @@ -93,7 +93,7 @@ The :mod:`crypt` module defines the following functions:
may be available on all platforms), or a full encrypted password
including salt, as returned by this function. If *salt* is not
provided, the strongest method will be used (as returned by
If methods is not a function, do we need the wording as returned by ? We
usually use return for results of functions and methods. Am assuming due
diligence, that methods is actually an attribute, not a method, therefore
someone else can confirm on this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#26806 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB3RIVW766O2V2LARPJZSLTUCCF3ANCNFSM467OMZVA>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Thanks @akulakov for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
GH-32324 is a backport of this pull request to the 3.10 branch. |
GH-32325 is a backport of this pull request to the 3.9 branch. |
Co-authored-by: Jelle Zijlstra <[email protected]> (cherry picked from commit cae0f5d) Co-authored-by: andrei kulakov <[email protected]>
Co-authored-by: Jelle Zijlstra <[email protected]> (cherry picked from commit cae0f5d) Co-authored-by: andrei kulakov <[email protected]>
@JelleZijlstra thanks for reviewing! |
Co-authored-by: Jelle Zijlstra <[email protected]> (cherry picked from commit cae0f5d) Co-authored-by: andrei kulakov <[email protected]>
Co-authored-by: Jelle Zijlstra <[email protected]> (cherry picked from commit cae0f5d) Co-authored-by: andrei kulakov <[email protected]>
Co-authored-by: Jelle Zijlstra <[email protected]> (cherry picked from commit cae0f5d) Co-authored-by: andrei kulakov <[email protected]>
No description provided.