-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-108202: calendar
: Document TextCalendar
methods
#127608
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
This comment was marked as outdated.
This comment was marked as outdated.
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.
Some initial comments. (I'll tag Erlend again once I consider this ready from a triage standpoint.)
It's probably worth converting the phrase "string representation" into a reference to the str
class.
Co-authored-by: Peter Bierma <[email protected]>
Co-authored-by: Peter Bierma <[email protected]>
Co-authored-by: Peter Bierma <[email protected]>
Co-authored-by: Peter Bierma <[email protected]>
As per ZeroIntenisities suggestion
Co-authored-by: Peter Bierma <[email protected]>
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.
Ok, I'll refrain from nitpicking. I don't know enough about calendar
to give this a green check, so I'll just tag Erlend.
@erlend-aasland All done now. In the future do you prefer a PR for every function like hugokvs maybe it is easier to review? |
No, do not create one PR for every function. Just don't mix different types of changes in a PR (nor in an issue). This is all explained in clear text in the devguide. |
@erlend-aasland ok. Is this PR ok for you then? Are there any other changes you want before you review? This PR was originally focused on just the functions but then expanded with suggestions from other reviewers, I have reverted all of them. |
I'm torn about these changes. If you take the time to read through this issue's history, you'll find that it is in fact pretty controversial. Some core devs actively oppose documenting methods that could/should be considered helpers and/or private APIs. Other core devs lean towards that every (intentional or unintentional) public API should be documented. There is no happy path. I guess I'm fine with this; since other similar calendar formatting helpers have been documented, we might as well document the rest of them. |
I see; I'm sorry about the extra work. I did not read through all of the previous remarks. I prefer to align strictly with our recommended development guidelines and strictly keep any type of change atomic. This implies:
As with any kind of rule, there will be exceptions. But exceptions are exceptions; if they become the new norm, our guidelines become moot. Keeping changes atomic has several positive effects:
Footnotes
|
@picnixz: if you are satisfied with this, feel free to land it. |
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.
A last markup change and we're good.
Co-authored-by: Bénédikt Tran <[email protected]>
(FTR, I still don't have the commit rights so you'll still need to hit the merge button @erlend-aasland :')) |
What?! Outrageous! 😄 |
This comment was marked as outdated.
This comment was marked as outdated.
…ythonGH-127608) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader() (cherry picked from commit bb73426) Co-authored-by: Stan Ulbrych <[email protected]>
…ythonGH-127608) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader() (cherry picked from commit bb73426) Co-authored-by: Stan Ulbrych <[email protected]>
GH-128440 is a backport of this pull request to the 3.13 branch. |
GH-128441 is a backport of this pull request to the 3.12 branch. |
…H-127608) (#128441) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader() (cherry picked from commit bb73426) Co-authored-by: Stan Ulbrych <[email protected]>
…H-127608) (#128440) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader() (cherry picked from commit bb73426) Co-authored-by: Stan Ulbrych <[email protected]>
…ython#127608) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader()
…ython#127608) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader()
#108202
📚 Documentation preview 📚: https://cpython-previews--127608.org.readthedocs.build/