Pandas version checks
-
[x] I have checked that this issue has not already been reported.
-
[x] I have confirmed this bug exists on the latest version of pandas.
-
[x] I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
python make.py html
Issue Description
The following error prevents doc/build/html/index.html from getting created. Here are the steps to reproduce.
- Pulled down from upstream/original Pandas
- Created an environment using Option 2 (pip) from https://pandas.pydata.org/docs/dev/development/contributing_environment.html
- Followed steps for building the documentation locally from https://pandas.pydata.org/docs/dev/development/contributing_documentation.html
- After running python make.py html, received a 'Sphinx parallel build error', 'Runtime unexpected exception' error in file
/doc/source/getting_started/comparison/comparison_with_sas.rst
line 135`
Screenshot of error
Machine: 2020 Macbook Pro 1.4 GHz Quad-Core Intel Core i5
Expected Behavior
I expected the docs to be built and for doc/build/html/index.html to be created.
Installed Versions
Comment From: jeffersbaxter
I tried to troubleshoot with:
python make.py clean python make.py html
Comment From: jeffersbaxter
I'm willing to resolve and open a PR if a team member decides that a PR is necessary. Let me know!
Comment From: jeffersbaxter
take
Comment From: rhshadrach
Thanks for the report. With the information provided, I do not believe there is anything more we can do. I would suggest trying to build the documentation with --num-jobs=1
and find what code around line 135 causes errors when run in isolation.
Comment From: jeffersbaxter
Thank you for your reply! I'll investigate this further with your suggested command and report what I find.
Comment From: jeffersbaxter
Your recommended command with the --num-jobs=1 flag helped to identify that I was having an issue locally with SSL. A new contributor like me might be naive to the fact that their local SSL config could cause the build to fail, which makes me think that adding this error case in the documentation could help future developers.
WIth this in mind, I have made a PR, for you to consider, if you think it would help. If not, no worries!