Uh oh!
There was an error while loading. Please reload this page.
gh-108202: calendar: Document TextCalendar methods - #127608
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
ZeroIntensity
left a comment
There was a problem hiding this comment.
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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
As per ZeroIntenisities suggestion
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
ZeroIntensity
left a comment
There was a problem hiding this comment.
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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
StanFromIreland
commented
Jan 1, 2025
@erlend-aasland All done now. In the future do you prefer a PR for every function like hugokvs maybe it is easier to review? |
erlend-aasland
commented
Jan 1, 2025
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. |
StanFromIreland
commented
Jan 1, 2025
@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. |
erlend-aasland
commented
Jan 2, 2025
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. |
erlend-aasland
commented
Jan 2, 2025
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
|
erlend-aasland
commented
Jan 2, 2025
@picnixz: if you are satisfied with this, feel free to land it. |
picnixz
left a comment
There was a problem hiding this comment.
A last markup change and we're good.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
picnixz
commented
Jan 3, 2025
(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 <89152624+StanFromIreland@users.noreply.github.com>
…ythonGH-127608) Document the following TextCalendar methods: - formatday() - formatmonthname() - formatweekday() - formatweekheader() (cherry picked from commit bb73426) Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
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. |
…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/