Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/source/python/getting_involved.rst
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ less complex to use. So while in some cases it might be easy to map what's
in C++ to what's in Python, in many cases the C++ classes and methods are
used as foundations to build easier to use entities.

.. image:: py_arch_overview.svg
.. image:: /python/images/py_arch_overview.svg
:alt: Four layers of PyArrow architecture: .py, .pyx, .pxd and low level C++ code.

* The ``*.py`` files in the pyarrow package are usually where the entities
Expand All @@ -69,7 +69,8 @@ used as foundations to build easier to use entities.
for usage in Cython. Here the C++ classes and methods are declared as they are
so that in the other ``.pyx`` files they can be used to implement Python classes,
functions and helpers.
* PyArrow is also based on dedicated pieces of code that are written into Arrow itself.
Those live into ``cpp/src/arrow/python`` directory and provide the low level
* Apart from Arrow C++ library, which dependence is mentioned in the previous line,
PyArrow is also based on PyArrow C++, dedicated pieces of code that live in
``python/pyarrow/src/arrow/python`` directory and provide the low level
code for capabilities like converting to and from numpy or pandas and the classes
that allow to use Python objects and callbacks in C++.
1 change: 1 addition & 0 deletions docs/source/python/images/py_arch_overview.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 0 additions & 1 deletion docs/source/python/py_arch_overview.svg

This file was deleted.