bpo-22377: Fixes documentation for %Z in datetime#16507
bpo-22377: Fixes documentation for %Z in datetime#16507miss-islington merged 5 commits intopython:masterfrom
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
Misc/NEWS.d/next/Documentation/2019-10-01-10-53-46.bpo-22377.5ni-iC.rst
Outdated
Show resolved
Hide resolved
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @pganssle: please review the changes made to this pull request. |
Do not hesitate to tell me if there is something else I can do. |
|
@karlcow You don't have to worry too much about squashing your commits down, the branch protection rules force us to do squash merges, and we can always squash at the end. |
|
@pganssle ok. Everything is set. Ready to merge if no more comments. Hands off. |
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @pganssle: please review the changes made to this pull request. |
…ni-iC.rst Co-Authored-By: Paul Ganssle <p.ganssle@gmail.com>
- Made the more unusual value more prominent. - Made a clearer separation between the `strptime` and `strftime` parts.
pganssle
left a comment
There was a problem hiding this comment.
I am so sorry it's taken me so long to swing back around to this @karlcow.
I made some minor tweaks here and everything looks good. Please take a look at my changes and let me know if you agree with my changes. If so, I'm happy to merge.
(By the way, I did a force-push because I rebased against master, if you need to make more changes, please do a force-pull or something equivalent first).
Let's go with it! |
|
Thanks @karlcow for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
|
I'm having trouble backporting to |
|
Sorry, @karlcow, I could not cleanly backport this to |
This fixes the issue discussed in https://bugs.python.org/issue22377 and fixes it according to the comments made by Paul Ganssle @pganssle * It clarifies which values are acceptable in the table * It extends the note with a clearer information on the valid values https://bugs.python.org/issue22377
This fixes the issue discussed in https://bugs.python.org/issue22377 and fixes it according to the comments made by Paul Ganssle @pganssle * It clarifies which values are acceptable in the table * It extends the note with a clearer information on the valid values https://bugs.python.org/issue22377
This fixes the issue discussed in https://bugs.python.org/issue22377
and fixes it according to the comments made by Paul Ganssle @pganssle
https://bugs.python.org/issue22377
Automerge-Triggered-By: @pganssle