Skip to content

bpo-22377: Fixes documentation for %Z in datetime#16507

Merged
miss-islington merged 5 commits intopython:masterfrom
karlcow:issue22377
Nov 26, 2019
Merged

bpo-22377: Fixes documentation for %Z in datetime#16507
miss-islington merged 5 commits intopython:masterfrom
karlcow:issue22377

Conversation

@karlcow
Copy link
Copy Markdown
Contributor

@karlcow karlcow commented Oct 1, 2019

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

Automerge-Triggered-By: @pganssle

@the-knights-who-say-ni
Copy link
Copy Markdown

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 username

We couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames:

@karlcow

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!

Copy link
Copy Markdown
Member

@pganssle pganssle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this looks great, thanks @karlcow!

I just have two minor nits.

@bedevere-bot
Copy link
Copy Markdown

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. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@karlcow
Copy link
Copy Markdown
Contributor Author

karlcow commented Oct 1, 2019

I have made the requested changes; please review again

@bedevere-bot
Copy link
Copy Markdown

Thanks for making the requested changes!

@pganssle: please review the changes made to this pull request.

@karlcow
Copy link
Copy Markdown
Contributor Author

karlcow commented Oct 4, 2019

@pganssle

  1. I introduced your comments
  2. Change a bit the order and the shape of the notes so it is less confusing.
  3. rebase it so that it will fit in one commit.
  4. force pushed.

Do not hesitate to tell me if there is something else I can do.

@karlcow karlcow requested a review from pganssle October 4, 2019 07:40
@pganssle
Copy link
Copy Markdown
Member

pganssle commented Oct 4, 2019

@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.

@karlcow
Copy link
Copy Markdown
Contributor Author

karlcow commented Oct 4, 2019

@pganssle ok. Everything is set. Ready to merge if no more comments. Hands off.
Thanks a lot for the help and the review.

@karlcow
Copy link
Copy Markdown
Contributor Author

karlcow commented Oct 9, 2019

I have made the requested changes; please review again

@bedevere-bot
Copy link
Copy Markdown

Thanks for making the requested changes!

@pganssle: please review the changes made to this pull request.

karlcow and others added 2 commits November 4, 2019 17:29
- Made the more unusual value more prominent.
- Made a clearer separation between the `strptime` and `strftime` parts.
Copy link
Copy Markdown
Member

@pganssle pganssle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

@karlcow
Copy link
Copy Markdown
Contributor Author

karlcow commented Nov 6, 2019

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.

Let's go with it!
Thanks.

@miss-islington miss-islington merged commit bc441ed into python:master Nov 26, 2019
@miss-islington
Copy link
Copy Markdown
Contributor

Thanks @karlcow for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8.
🐍🍒⛏🤖

@miss-islington
Copy link
Copy Markdown
Contributor

I'm having trouble backporting to 3.8. Reason: 'Error 110 while writing to socket. Connection timed out.'. Please retry by removing and re-adding the needs backport to 3.8 label.

@miss-islington
Copy link
Copy Markdown
Contributor

Sorry, @karlcow, I could not cleanly backport this to 3.7 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker bc441ed7c1449f06df37905ee6289aa93b85d4cb 3.7

@miss-islington miss-islington self-assigned this Nov 26, 2019
jacobneiltaylor pushed a commit to jacobneiltaylor/cpython that referenced this pull request Dec 5, 2019
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
shihai1991 pushed a commit to shihai1991/cpython that referenced this pull request Jan 31, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation in the Doc dir

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants