[
https://issues.apache.org/jira/browse/ARROW-17320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577330#comment-17577330
]
Joris Van den Bossche commented on ARROW-17320:
-----------------------------------------------
On second thought, I think it is maybe fine to just "break" this is a next
release by explicitly defining the {{\_\_all\_\_}}. If someone would run into
it, it is easy to fix in your code.
But starting to add deprecation warnings for those sounds quite onerous for the
value it would provide.
(we only need to remember to add {{\_filters_to_expression}} to the list, since
that is used by other projects)
> [Python] Refine pyarrow.parquet API exposure
> --------------------------------------------
>
> Key: ARROW-17320
> URL: https://issues.apache.org/jira/browse/ARROW-17320
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Parquet, Python
> Reporter: Miles Granger
> Priority: Major
>
> Spawning from ARROW-17106, moving code from `pyarrow/parquet/_init_{_}` to
> `pyarrow/parquet/core` and re-exporting in `_i{_}{_}nit_{_}` to maintain the
> same functionality.
> [pyarrow._init_|https://github.com/apache/arrow/blob/master/python/pyarrow/__init__.py]is
> very careful about what is exposed through the public API by prefixing
> private symbols with underscores, even imports.
> What's exposed at the top level of `{{{}pyarrow.parquet{}}}`, however, is not
> so careful. API calls such as `{{{}pq.FileSystem{}}}`, `{{{}pq.pa.Array{}}}`,
> `{{{}pq.json{}}}` are all valid and should probably be designated as private
> attributes in {{{}pyarrow.parquet{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
