gh-99032: datetime docs: Encoding is no longer relevant#93365
Merged
pganssle merged 3 commits intopython:mainfrom Apr 24, 2023
wjandrea:patch-2
Merged
gh-99032: datetime docs: Encoding is no longer relevant#93365pganssle merged 3 commits intopython:mainfrom wjandrea:patch-2
pganssle merged 3 commits intopython:mainfrom
wjandrea:patch-2
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
.strftime()methods return a Unicode string as of Python 3.0.For reference, under the hood, the
.strftime()methods usetime.strftime(), whose return value is defined here for the current tip of the main branch and here for 3.0.Please check my work before merging to make sure I've understood what the docs are saying. I'm also not super familiar with C or RST, but I'm quite sure I've understood them correctly.
Backports should be made to all current versions.
BTW, encoding isn't mentioned in the
timedocs, so no changes required there I don't think.