@apurvakhatri please could you split this PR into two parts? We haven't discussed if we want to document mdays, so having both in one PR makes it difficult to review.

A

Sure, will do that! Should I create a new PR or just remove mdays from this PR request?

The latter is likely easier. Perhaps also consider documenting all prweek() instances in this PR, rather than just TextCalendar.prweek().

A

@apurvakhatri please avoid force pushes, see the devguide:

Your pull request may involve several commits as a result of addressing code review comments. Please keep the commit history in the pull request intact by not squashing, amending, or anything that would require a force push to GitHub. A detailed commit history allows reviewers to view the diff of one commit to another so they can easily verify whether their comments have been addressed. The commits will be squashed when the pull request is merged.

Please also restrict this PR to just prweek(), as discussed.

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.