You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pasting my comment from #61386 for visibility with relevant decisionmakers
As promised during the sync meeting today, I went and compiled how various read functions handle columns being specified. Functions that take usecols (read_csv, read_clipboard, read_excel, and read_hdf(undocumented)) don't take into account input order, whereas functions that ask for columns instead do (hdf, feather, parquet, orc, starata, sql).
Finally, there are also some that straight up don't take column specifiers.
I'd expect functions that use usecols to be using the same function in the backend, but I'd have to verify it if we're planning to standardize the parameter.
CSV attached below of functions tested (those with a read and write function in pandas) does_it_use_order.csv
The text was updated successfully, but these errors were encountered:
pasting my comment from #61386 for visibility with relevant decisionmakers
The text was updated successfully, but these errors were encountered: