CI: Enable spellcheck in docbuild

[TomAugspurger]

Followup to #21109

We'll need to refactor scripts/announce.py to update the list of contributors on each build.

Then we can enable spellcheck in the Travis doc build.

[daminisatya]

Is this issue still open? @TomAugspurger

[FabioRosado]

I would like to take on this since this is related to my previous PR 😄

[FabioRosado]

@daminisatya Apologies I had this tab open and your comment didnt show but you beat me to it so if you would like to take on this issue go ahead 😄 👍

[WillAyd]

@daminisatya since you marked interest in this and the JSON issue how about you tackle the JSON one as a first contribution and let @FabioRosado continue with this one, since this is a logical follow up to a change he just made?

[daminisatya]

Yes @WillAyd, I was about to comment the same :) @FabioRosado you can go ahead with the issue since you have already solved it you will have a better context than me! I took up another first-timer issue.

[afeld]

Update: Appears this was added and then subsequently removed. In #24287, the comment that:

The spellcheck system was implemented, but with dependencies (i.e. enchant) that are no longer maintained, and there is no reasonable way to set them up.

doesn't seem to be true anymore. I'm seeing releases for both enchant and pyenchant in December 2020. In other words, I think we should consider adding spellcheck back in.

[afeld]

Currently we run codespell on the source code, minus the test suite.

pandas/.pre-commit-config.yaml

Lines 202 to 205 in 00ddacf

	- id: codespell
	types_or: [python, rst, markdown]
	files: ^pandas/
	exclude: ^pandas/tests/

We could expand it to the docs and see how it compares…?

[MarcoGorelli]

@afeld yes, there's an open issue about that #38802

[afeld]

Seems like the issues are duplicates, so closing this one for now.