BUG: raise TypeError when array not like 1D in pandas.array

[antareepsarkar]

• resolves BUG: pandas.array works fine when 2-D array contains string #63112
• Tests added and passed.
• All code checks passed.

Follows from #63173. I'm Sorry, but the last commit of the PR showed "Processing updates" for a long time. So, I closed that.

[antareepsarkar]

@Alvaro-Kothe
This time, I have used np.array() for it to be time efficient like the _from_sequence method.
Many parts of pandas require _from_sequence to convert objects to their string representations. So, many files needed to be changed. I did not modify it.

If I have done some mistake or any change is required, please tell me.

[Alvaro-Kothe]

This time, I have used np.array() for it to be time efficient like the _from_sequence method.

There are some benchmarks for array construction in asv_bench/benchmarks/array.py that you can use to measure performance impact. For guidance on how to run it, refer to the docs.

[Alvaro-Kothe]

I don't like this for the following reasons:

1. It's weird to convert to np.array while calling pd.array and not use it.
2. The conversion in np.array can raise, e.g., when we call np.array([[1, 2], ["a"]]).

[antareepsarkar]

Is this change alright? Do I need to make any changes?

[Alvaro-Kothe]

Can you run the benchmarks?

[antareepsarkar]

Can you run the benchmarks?

I ran the benchmarks. The last commit has decreased the efficiency. Sorry for that.
I came after this issue #61155 which was resolved. So, maybe we can just update the docs for this behavior of pandas.array.