It's unclear why one would want to deal with an API response as a pandas object. Since "pandas" became an option of the response return type in both this codebase and its internal, private precursor 8+ years ago, it has seen zero internal usage. From users external to Civis, the one time we heard about this usage was when an error was raised (see the linked internal ticket) 4 years ago. All this is to say, it's time to simply drop this "pandas" option to avoid further confusion.
[x] (For Civis employees only) Reference to a relevant ticket in the pull request title
[x] Changelog entry added to CHANGELOG.md at the repo's root level
[x] Description of change in the pull request description
[x] If applicable, unit tests have been added and/or updated
It's unclear why one would want to deal with an API response as a pandas object. Since
"pandas"became an option of the response return type in both this codebase and its internal, private precursor 8+ years ago, it has seen zero internal usage. From users external to Civis, the one time we heard about this usage was when an error was raised (see the linked internal ticket) 4 years ago. All this is to say, it's time to simply drop this"pandas"option to avoid further confusion.CHANGELOG.mdat the repo's root level