bpo-9004: Recommend against using utctimetuple in the docs. - #10870
bpo-9004: Recommend against using utctimetuple in the docs.#10870abalkin wants to merge 1 commit into
Conversation
Sorry, something went wrong.
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. |
Sorry, something went wrong.
| 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.
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"
Sorry, something went wrong.
There was a problem hiding this comment.
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 ...
Sorry, something went wrong.
|
I think maybe we should consolidate this into #15773. @nanjekyejoannah Do you mind adding a similar warning box to .utctimetuple()? I don't think I even realized that this function exists 😞 |
Sorry, something went wrong.
Closes bpo-9004.
Original patch by Gaurav Tatke.
https://bugs.python.org/issue9004