-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: use black to fix code style in doc pandas-dev#36777 #36813
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
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.
Looks good, thanks @PrayagS
Actually may have approved too quickly, looks like there are some linting errors |
Seems like the latest commit fixed all the linting errors. Please have a look again. |
@PrayagS I'm not too familiar with how Hacktoberfest works, but I think you should be good since the PR was merged. As far as I can tell the Hacktoberfest label is optional (we don't have one). |
So sorry to disturb again but Hacktoberfest has undergone some changes due to the excessive spamming that occurred this year. The rules for a PR to be accepted have been modified. You can read about it here: https://hacktoberfest.digitalocean.com/hacktoberfest-update Here is the most important part for maintainers: I can completely understand if pandas as an org doesn't do this but just notifying in case. |
@PrayagS Ah, looks like we probably do need to add the hacktoberfest topic. Can you create an issue about that? |
Partially addresses #36777. Ran black on all the files under
doc/source/getting_started/comparison
.