DEPR: create_block_manager_from_blocks

[jbrockmendel]

No description provided.

[mroeschke]

Are you aware of any libraries using this?

[jbrockmendel]

Are you aware of any libraries using this?

@phofl says dask is using it

[phofl]

Yep, I’d prefer not to deprecate

[jbrockmendel]

im pretty set on this; we need to ween dask and anyone else off of internals in general if we want to be able to change anything. in particular i want to get the axes out of the Managers

[phofl]

We are serializing/de-serializing the blocks. I am open to do this differently though, but not sure if there is an efficient way of doing this

[jbrockmendel]

We are serializing/de-serializing the blocks. I am open to do this differently though, but not sure if there is an efficient way of doing this

Create a DataFrame for each block and concat them?

[phofl]

Can we offer a private api for this maybe? List of blocks and axes?

[jbrockmendel]

Can we offer a private api for this maybe? List of blocks and axes?

After this PR dask can get continue to import the function from internals.api which is explicitly pseudo-public for pyarrow/dask. This PR is just getting the function to the more-correct place.

Long-term, no. dask and anyone else need to stop using Blocks/Managers directly.

[jreback]

lgtm