e
> > (python/pyarrow/compute.py), and then that is used to build actual
> reSt
> > docs when docs are built
> >
> > *Proposal?*:
> > How about having a subdirectory for doc additions written in reStructured
> > text that looks a lot like regula
St
docs when docs are built
*Proposal?*:
How about having a subdirectory for doc additions written in reStructured
text that looks a lot like regular functional docs. This provides a single,
easy to find location for the custom python docs (solving #3 and some of
#4) and examples can be tested
y), and then that is used to build actual reSt
docs when docs are built
*Proposal?*:
How about having a subdirectory for doc additions written in reStructured
text that looks a lot like regular functional docs. This provides a single,
easy to find location for the custom python docs (solving #3
Wes McKinney created ARROW-8275:
---
Summary: [Python][Docs] Review Feather + IPC file documentation
per "Feather V2" changes
Key: ARROW-8275
URL: https://issues.apache.org/jira/browse/ARROW-8275
hi Alex,
Documentation contributions are treated equivalently to code
contributions as far as process -- if you run into problems, let us
know on the mailing list or JIRA/GitHub.
> While reviewing the docs I also noticed this page has a TODO -
> https://arrow.apache.org/docs/python/data.html. Is
Hi,
I've come across a couple StackOverflow questions and JIRA tickets looking for
updates to the PyArrow documentation. I thought this might be a good way for me
to get more familiar with the code base while also contributing back. I went
throught JIRA trying to find all the Python documentati
