-
-
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
clarify distinction between datetime module and class in deprecation messages #108073
clarify distinction between datetime module and class in deprecation messages #108073
Conversation
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.
Could you please fix also datetime.utcnow()
?
e0570a5
to
29c0fad
Compare
@serhiy-storchaka done ! |
Ping @Yhg1s for merge ? |
Thanks @neutrinoceros for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
GH-108540 is a backport of this pull request to the 3.12 branch. |
…messages (pythonGH-108073) (cherry picked from commit 09343db) Co-authored-by: Clément Robert <[email protected]>
…cation messages (GH-108073) (#108540) Clarify distinction between datetime module and class in deprecation messages (GH-108073) (cherry picked from commit 09343db) Co-authored-by: Clément Robert <[email protected]>
Lib/_pydatetime.py says:
Modules/_datetimemodule.c says:
and similar for utcfromtimestamp. Inconsistent. |
I noticed this deprecation warning used
datetime
to refer to the module and the class on the same line (UTC
is a module level constant whilefromtimestamp
is a class method).