DOC: Fix minor typos and capitalization in community tutorials #62350
Conversation
Fixed small issues in the community tutorials page: - Changed "lesson" → "lessons" - Made "Modern Pandas" heading consistent - Capitalized "Pandas Cookbook"
| * `Using Pandas and XlsxWriter to create Excel charts <https://pandas-xlsxwriter-charts.readthedocs.io/>`_ | ||
|
|
||
| Joyful pandas | ||
| Modern pandas |
There was a problem hiding this comment.
I realize now that 'Joyful Pandas' is the original title. I initially changed it to 'Modern Pandas' to keep the headings uniform and professional, similar to other tutorial sections. If preferred, I can revert it back to 'Joyful Pandas'
|
Yes
…On Tue, 16 Sep 2025 at 8:42 PM, andrewf28 ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In doc/source/getting_started/tutorials.rst
<#62350 (comment)>:
> @@ -75,7 +75,7 @@ Excel charts with pandas, vincent and xlsxwriter
* `Using Pandas and XlsxWriter to create Excel charts <https://pandas-xlsxwriter-charts.readthedocs.io/>`_
-Joyful pandas
+Modern pandas
It looks like it's fixing typos
—
Reply to this email directly, view it on GitHub
<#62350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BWIKNQDSFGUYLDPVBF7DN7L3TAVVLAVCNFSM6AAAAACGVAL6K2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTEMZQGYYTINBXGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
| This is a guide to many pandas tutorials by the community, geared mainly for new users. | ||
|
|
||
| pandas cookbook by Julia Evans | ||
| Pandas Cookbook by Julia Evans |
There was a problem hiding this comment.
Why should this heading be capitalized when the next one is not?
explain to me the difference between Cookbook and workshop
There was a problem hiding this comment.
Thanks for asking. I capitalized “Pandas Cookbook” because it refers to a specific published resource, so it makes sense to treat it as a proper title. On the other hand, “pandas workshop” feels more like a descriptive label for a workshop rather than a formal title, so I left it in lowercase
There was a problem hiding this comment.
Both are named resources with dedicated GitHub repositories, structured content, and clear authorship. In fact, the “pandas workshop” has been presented at PyCon US, SciPy, and multiple international conferences, and includes a formal license and publication history. That’s arguably more “formally titled” than the Cookbook, which is a personal project.
Both resources are titled and curated—not generic or ephemeral.
Both are GitHub-hosted collections of Jupyter notebooks, making them structurally equivalent.
The workshop even references a published book (“Hands-On Data Analysis with Pandas”) by the same author, adding to its formal pedigree.
So the distinction feels arbitrary. If “Pandas Cookbook” deserves capitalization for being a named resource, then “Pandas Workshop” should too—especially given its professional delivery and licensing.
By labeling it as a “descriptive label” and leaving it lowercase—while capitalizing “Pandas Cookbook”— this implies a hierarchy of formality or importance that doesn’t hold up under scrutiny. That framing could be seen as diminishing the workshop’s legitimacy, especially since it’s arguably more professionally curated than the Cookbook.
There was a problem hiding this comment.
Thank you for pointing this out. You’re right that both Pandas Cookbook and pandas workshop are established, curated resources with dedicated repositories and authorship. For the sake of consistency, I’m happy to adjust the formatting so that both are either capitalized or left lowercase, depending on the project’s style preference. Please let me know which option you’d like, and I’ll update the PR accordingly
|
Thanks again for the contribution and for engaging thoughtfully with the feedback. After reviewing the changes and the surrounding discussion, I think it’s best to leave the original formatting and titles as-is and that the proposed edits are not necessary at this time. I’ll go ahead and close the PR, but thank you again for taking the time to submit it—and I hope you’ll consider contributing again in the future. |
|
Thank you for taking the time to review my contribution and for the
thoughtful feedback. I completely understand the decision to keep the
original formatting, and I appreciate the guidance I received through this
process. I’ve learned a lot and will definitely look forward to
contributing again in the future
…On Wed, 17 Sep 2025 at 4:00 PM, Simon Hawkins ***@***.***> wrote:
*simonjayhawkins* left a comment (pandas-dev/pandas#62350)
<#62350 (comment)>
Thanks again for the contribution and for engaging thoughtfully with the
feedback.
After reviewing the changes and the surrounding discussion, I think it’s
best to leave the original formatting and titles as-is and that the
proposed edits are not necessary at this time.
I’ll go ahead and close the PR, but thank you again for taking the time to
submit it—and I hope you’ll consider contributing again in the future.
—
Reply to this email directly, view it on GitHub
<#62350 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BWIKNQFQUHXUTQQQZYXCBQT3TE5OTAVCNFSM6AAAAACGVAL6K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBSGQ2TQMZUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
2 participants
Fixed small issues in the community tutorials page:
Changed "lesson" → "lessons"
Made "Modern Pandas" heading consistent
Capitalized "Pandas Cookbook"
closes #xxxx (Replace xxxx with the GitHub issue number)
Tests added and passed if fixing a bug or adding a new feature
All code checks passed.
Added type annotations to new arguments/methods/functions.
Added an entry in the latest
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.