GH-35403: [Docs] Support sphinx 6 for building the docs

ci/conda_env_sphinx.txt

@@ -21,9 +21,11 @@ doxygen
 ipython
 numpydoc
 pydata-sphinx-theme==0.8
+sphinx-autobuild
 sphinx-design
-sphinx>=4.2,<6
 sphinx-copybutton
+sphinxcontrib-jquery
+sphinx==6.2
 # Requirement for doctest-cython
 pytest-cython
 pandas

docs/Makefile

@@ -150,6 +150,8 @@ cpp-live:
 
 .PHONY: python
 python:
+	# Remove the following line when sphinx issue (https://github.com/sphinx-doc/sphinx/issues/10943) is closed
+	python -m pip install ../python --quiet --no-dependencies
 	$(SPHINXBUILD) -b html $(SPHINXOPTS) -c $(SOURCEDIR) $(SOURCEDIR)/python $(BUILDDIR)/html/python
 	@echo
 	@echo "Build finished. The HTML files are in $(BUILDDIR)/html/python"

docs/requirements.txt

@@ -9,5 +9,6 @@ pydata-sphinx-theme==0.8
 sphinx-autobuild
 sphinx-design
 sphinx-copybutton
-sphinx>=4.2,<6
+sphinxcontrib-jquery
+sphinx==6.2
 pandas

docs/source/conf.py

@@ -115,6 +115,7 @@
     'IPython.sphinxext.ipython_console_highlighting',
     'IPython.sphinxext.ipython_directive',
     'numpydoc',
+    "sphinxcontrib.jquery",
     'sphinx_design',
     'sphinx_copybutton',
     'sphinx.ext.autodoc',

docs/source/cpp/build_system.rst

@@ -45,6 +45,7 @@ This minimal ``CMakeLists.txt`` file compiles a ``my_example.cc`` source
 file into an executable linked with the Arrow C++ shared library:
 
 .. code-block:: cmake
+
    cmake_minimum_required(VERSION 3.16)
 
    project(MyExample)

docs/source/developers/documentation.rst

@@ -87,6 +87,14 @@ These two steps are mandatory and must be executed in order.
    not sufficiently comprehensive. Portions of the Python API documentation
    will also not build without CUDA support having been built.
 
+.. note::
+
+   If you are working on the Python documentation and are building the documentation
+   with ``pyarrow`` build from source on macOS Monterey, Python section of the
+   documentation might not be included in the ``_build/html`` when using the
+   ``make html`` command. In this case use ``make python`` to only build the
+   python part of the documentation.
+
 After these steps are completed, the documentation is rendered in HTML
 format in ``arrow/docs/_build/html``.  In particular, you can point your browser
 at ``arrow/docs/_build/html/index.html`` to read the docs and review any changes

docs/source/developers/java/building.rst

@@ -195,7 +195,7 @@ CMake
 
 - To build all JNI libraries (MacOS / Linux) except the JNI C Data Interface library:
 
-  .. code-block::
+  .. code-block:: text
 
       $ cd arrow
       $ brew bundle --file=cpp/Brewfile

docs/source/format/CDeviceDataInterface.rst

@@ -282,7 +282,7 @@ has the following fields:
     data.
 
 .. seealso::
-    The :ref:`synchronization event types <_c-device-data-interface-event-types>`
+    The :ref:`synchronization event types <c-device-data-interface-event-types>`
     section below.
 
 .. c:member:: int64_t ArrowDeviceArray.reserved[3]
@@ -563,7 +563,7 @@ streaming source of Arrow arrays. It has the following fields:
 .. c:member:: ArrowDeviceType device_type
 
     *Mandatory.* The device type that this stream produces data on. All
-    ``ArrowDeviceArray``s that are produced by this stream should have the
+    ``ArrowDeviceArray`` s that are produced by this stream should have the
     same device type as is set here. This is a convenience for the consumer
     to not have to check every array that is retrieved and instead allows
     higher-level coding constructs for streams.
@@ -675,7 +675,7 @@ is frozen. This means that the ``ArrowDeviceArray`` structure definition
 should not change in any way -- including adding new members.
 
 Backwards-compatible changes are allowed, for example new macro values for
-:c:typedef:`ArrowDeviceType` or converting the reserved 24 bytes into a
+:c:type:`ArrowDeviceType` or converting the reserved 24 bytes into a
 different type/member without changing the size of the structure.
 
 Any incompatible changes should be part of a new specification, for example