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
arw2019 opened this issue
Jan 24, 2021
· 1 comment
· Fixed by #42669
Assignees
Labels
InternalsRelated to non-user accessible pandas implementationIO DataIO issues that don't fit into a more specific labelRefactorInternal refactoring of code
pyarrow requires BytesIO not StringIO so in #38370 we add a class that returns a binary handle to reader input. This class (BytesIOWrapper) should be integrated into IOHandle to better align with the patterns we use elsewhere for file handles (#37639 is the PR that standardized things)
I originally intended to do this in #38370 but I got a little stuck and since that PR is sizeable already I think it's better to spin it off into a separate follow-on task
The text was updated successfully, but these errors were encountered:
arw2019
added
Bug
Needs Triage
Issue that has not been reviewed by a pandas team member
Refactor
Internal refactoring of code
IO CSV
read_csv, to_csv
IO Data
IO issues that don't fit into a more specific label
Internals
Related to non-user accessible pandas implementation
and removed
Bug
IO Data
IO issues that don't fit into a more specific label
labels
Jan 24, 2021
Going to be taking this one now. The main use case for this would be pyarrow reading text data, so would be CSV and maybe JSON if we want that in the future.
InternalsRelated to non-user accessible pandas implementationIO DataIO issues that don't fit into a more specific labelRefactorInternal refactoring of code
references:
pyarrow requires
BytesIO
notStringIO
so in #38370 we add a class that returns a binary handle to reader input. This class (BytesIOWrapper
) should be integrated intoIOHandle
to better align with the patterns we use elsewhere for file handles (#37639 is the PR that standardized things)I originally intended to do this in #38370 but I got a little stuck and since that PR is sizeable already I think it's better to spin it off into a separate follow-on task
The text was updated successfully, but these errors were encountered: