[Python] Remove backward compatibility hacks from pyarrow.pandas_compat

[asfimport]

This code is growing less maintainable. I think we can remove these backwards compatibility hacks since there are released versions of pyarrow that can be used to read old metadata and "fix" Parquet files if need be

Reporter: Wes McKinney / @wesm

Related issues:

• [Python] Bump minimum support pandas version to pandas 1.0 (relates to)

_{Note: This issue was originally created as ARROW-4830. Please see the migration documentation for further details.}

[asfimport]

Antoine Pitrou / @pitrou: @jorisvandenbossche

[asfimport]

Joris Van den Bossche / @jorisvandenbossche: For this, I think we should ideally decide on which minimum version of pyarrow we want to support (and then also test for this). Or at least we have something to communicate about like: "files written by pyarrow >= xx can be read"

[asfimport]

Neal Richardson / @nealrichardson: @jorisvandenbossche  is there action to be taken here still, and if so, can this be done for 4.0?

[asfimport]

Joris Van den Bossche / @jorisvandenbossche: Yes, there is a clean-up that can be done, but I don't think it is critical for 4.0.0, so moving to 5.0.0

[asfimport]

Todd Farmer / @toddfarmer: This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

[github-actions[bot]]

This issue has been marked as stale because it has had no activity in the past 365 days. Please remove the stale label or comment below, or this issue will be closed in 14 days. If this improvement is still desired but has no current owner, please add the 'Status: needs champion' label.