nchammas opened a new pull request #27390: [SPARK-30672] [BUILD] Add numpy to 
API docs readme
URL: https://github.com/apache/spark/pull/27390
 
 
   ### What changes were proposed in this pull request?
   
   This PR adds `numpy` to the list of things that need to be installed in 
order to build the API docs. It doesn't add a new dependency; it just documents 
an existing dependency.
   
   ### Why are the changes needed?
   
   You cannot build the PySpark API docs without numpy installed. Otherwise you 
get this series of errors:
   
   ```
   $ SKIP_SCALADOC=1 SKIP_RDOC=1 SKIP_SQLDOC=1 jekyll serve
   Configuration file: .../spark/docs/_config.yml
   Moving to python/docs directory and building sphinx.
   sphinx-build -b html -d _build/doctrees   . _build/html
   Running Sphinx v2.3.1
   loading pickled environment... done
   building [mo]: targets for 0 po files that are out of date
   building [html]: targets for 0 source files that are out of date
   updating environment: 0 added, 2 changed, 0 removed
   reading sources... [100%] pyspark.mllib                      
   WARNING: autodoc: failed to import module 'ml' from module 'pyspark'; the 
following exception was raised:
   No module named 'numpy'
   WARNING: autodoc: failed to import module 'ml.param' from module 'pyspark'; 
the following exception was raised:
   No module named 'numpy'
   ...
   ```
   
   ### Does this PR introduce any user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   Manually, by building the API docs with and without numpy.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to