-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
gh-106392: Fix inconsistency in deprecation warnings #106436
Conversation
They used "datetime" to refer to both the object and the module
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.
Thank you!
Thanks @wjandrea for the PR, and @hauntsaninja for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
GH-108792 is a backport of this pull request to the 3.12 branch. |
…106436) They used "datetime" to refer to both the object and the module. (cherry picked from commit d5c5d4b) Co-authored-by: William Andrea <[email protected]>
|
… (#108792) gh-106392: Fix inconsistency in deprecation warnings (GH-106436) They used "datetime" to refer to both the object and the module. (cherry picked from commit d5c5d4b) Co-authored-by: William Andrea <[email protected]>
Previously python#106436 fixed consistency within the suggested replacement, but not in the entire message
They used "datetime" to refer to both the object and the module