BUG: Assignment of pyarrow arrays yield unexpected dtypes

[droussea2001]

• closes BUG: Assignment of pyarrow arrays yields unexpected dtypes #56994
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• [N.A.] Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/v3.0.0.rst file if fixing a bug or adding a new feature.

During a column assignment in a DataFrame:

• If the column value is a pyarrow array (check tested with lib.is_pyarrow_array) sanitize_array sets dtype to ArrowDtype(value.type)
• Else the standard sanitize_array processing are applied

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[droussea2001]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

I'm still working on it.

[droussea2001]

@jorisvandenbossche : Hello Joris, hope you're doing well would you have any news about BUG: Assignment of pyarrow arrays yields unexpected dtypes ? Previously I was saying that "if a Series or a DataFrame is created or assigned with data dtype 'X' I would expect if it is possible, that it keeps the same 'X' dtype" but its only my humble opinion :-) and I would be equally happy to talk about it : maybe there is somewhere a discussion about how pyarrow types could be managed ? (thanks in advance !)

[rhshadrach]

Friendly ping @jorisvandenbossche

[droussea2001]

Hello @WillAyd: do you think this PR could be validated or should I have another approach ?

[WillAyd]

Looks pretty good but a few things still needed I think. Thanks for keeping this concise

[WillAyd]

lgtm although I see @jorisvandenbossche has some comments on the original issue. Let's clarify those before merging