ARROW-2593: [Python] TypeError: data type "mixed-integer" not understood

[kszucs]

Both name and field_name is enforced to be a string, but that way we lose the type of it (an integer in this case).
Could We use one of it to preserve the original type of the column name?

[codecov-io]

Codecov Report

Merging #2084 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2084      +/-   ##
==========================================
- Coverage   86.35%   86.33%   -0.02%     
==========================================
  Files         242      230      -12     
  Lines       41184    40297     -887     
==========================================
- Hits        35564    34791     -773     
+ Misses       5620     5506     -114

Impacted Files	Coverage Δ
python/pyarrow/pandas_compat.py	97.82% <ø> (ø)	⬆️
python/pyarrow/tests/test_convert_pandas.py	94.81% <100%> (+0.02%)	⬆️
rust/src/array.rs
rust/src/memory.rs
rust/src/list_builder.rs
rust/src/list.rs
rust/src/error.rs
rust/src/lib.rs
rust/src/memory_pool.rs
rust/src/builder.rs
... and 5 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce23c06...0e6d533. Read the comment docs.

[wesm]

+1. I think it's OK to coerce the integer to a string for now. If round-tripping this data faithfully becomes a problem, we can dig more into solutions later on

[xhochy]

+1, LGTM

I'm also happy with coercing to string at the moment.

[absognety]

pyarrow upgrade to 0.15.1 fixed this issue. with 0.9.0 his issue remains unresolved.

[wesm]

Right, the first release that contained this fix was 0.10.0