-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
bpo-9004: Recommend against using utctimetuple in the docs. #10870
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
Conversation
Closes issue 9004. Original patch by Gaurav Tatke.
@abalkin please add a news entry. You can use https://blurb-it.herokuapp.com/ to do this. |
@@ -742,6 +742,8 @@ Other constructors, all class methods: | |||
If *tz* is not ``None``, it must be an instance of a :class:`tzinfo` subclass, and the | |||
current date and time are converted to *tz*’s time zone. In this case the | |||
result is equivalent to ``tz.fromutc(datetime.utcnow().replace(tzinfo=tz))``. | |||
It is recommended to create aware datetime object for current UTC time 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.
Am not a native english speaker but shouldn't this "It is recommended to create aware datetime object " be "It is recommended to create an aware datetime object for current" or "be "It is recommended to create aware datetime objects for current"
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.
Am not a native english speaker neither but I'd propose:
The recommended way to create aware datetime object for the current time in UTC is ...
cc @pganssle |
I think maybe we should consolidate this into #15773. @nanjekyejoannah Do you mind adding a similar warning box to |
Closed in favor of #15773 |
Closes bpo-9004.
Original patch by Gaurav Tatke.
https://bugs.python.org/issue9004