REF: names no longer needed in _form_blocks, create_block_manager_from_arrays

[jbrockmendel]

1. copy/paste create_block_manager_from_arrays and _form_blocks to the pseudo-public internals.api
2. rename create_block_manager_from_arrays -> create_block_manager_from_column_arrays
3. prune no-longer-needed args from create_block_manager_from_arrays, _form_blocks

Two follow-ups after this:
4) remove no-longer-needed checks in no-longer-pseudo-public create_block_manager_from_column_arrays
5) deprecate pseudo-public create_block_manager_from_arrays

[jreback]

5. deprecate pseudo-public create_block_manager_from_arrays

yeah we think pyarrow (and maybe fastparquet) uses this internal api?

[jbrockmendel]

yeah we think pyarrow (and maybe fastparquet) uses this internal api?

yah will have to see when the time comes

[jbrockmendel]

failure is codecov

looking on github for external uses of create_block_manager_from_arrays and mostly just seeing it in pandas forks

[jreback]

kk great. lookign forward to code deletions.

[jorisvandenbossche]

I don't think that pyarrow or fastparquet use this (in any case pyarrow doesn't, xref #40226).

[jbrockmendel]

great, let's rip it out and see if anyone complains

[jbrockmendel]

cc @TomAugspurger looks like we kept create_block_manager_from_arrays in the internals namespace for dask. Is it still needed?

[jbrockmendel]

Looks like that was just the other function create_block_manager_from_blocks

[jorisvandenbossche]

Ah, yes, dask/partd uses create_block_manager_from_blocks (https://github.com/dask/partd/blob/main/partd/pandas.py)