[
https://issues.apache.org/jira/browse/ARROW-17819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608776#comment-17608776
]
Joris Van den Bossche commented on ARROW-17819:
-----------------------------------------------
BTW, for the conda install taking a long time: that's a common issue if you
already have a complex environment. In general I would recommend to use mamba
instead (but let's move this conversation elsewhere)
> [Doc] Remove dependency on PyArrow from rst build process
> ---------------------------------------------------------
>
> Key: ARROW-17819
> URL: https://issues.apache.org/jira/browse/ARROW-17819
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation
> Reporter: Larry White
> Priority: Major
>
> The process for building the tutorial documentation (see:
> apache/arrow/docs/source/developers/documentation.rst) identifies PyArrow as
> a requirement
> Ideally, it would not be necessary to install PyArrow to modify text
> documentation for Java or any other language.
> FWIW, On my machine, the PyArrow install has been running for over 20 minutes
> with repeated failure messages:
> {{conda install -c conda-forge pyarrow}}
> {{Collecting package metadata (current_repodata.json): done}}
> {{Solving environment: failed with initial frozen solve. Retrying with
> flexible solve.}}
> {{Solving environment: failed with repodata from current_repodata.json, will
> retry with next repodata source.}}
> {{Collecting package metadata (repodata.json): done}}
> {{Solving environment: failed with initial frozen solve. Retrying with
> flexible solve.}}
> {{Solving environment: |}}
> At this point I cancelled this and used pip to install, which finished
> successfully almost immediately. However, the next step (run {_}*python
> setup.py install*{_}) also failed. And failed again when I tried to run it in
> a dedicated Conda environment.
> Rather than continue with that, I tried to run the java documentation script:
> (run *_make java_tutorial_* in the arrow docs folder) and it was able to
> execute without issue, so I could see my changes as HTML.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
