-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: read_csv() crashes with engine='c' #14125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
this was likely fixed by: #13788 can you try. |
This still gives an error for me with latest master. |
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Nov 30, 2016
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
BUG: Fixed incorrect stream size check (pandas-dev#14125) Fixed after merge flake differences
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
BUG: Fixed incorrect stream size check (pandas-dev#14125) Fixed after merge flake differences Fixed char pointer spacing
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 23, 2017
4 tasks
jeffcarey
added a commit
to jeffcarey/pandas
that referenced
this issue
Jan 24, 2017
AnkurDedania
pushed a commit
to AnkurDedania/pandas
that referenced
this issue
Mar 21, 2017
closes pandas-dev#14125 Previously, self->stream_cap was copied into a local variable called maxstreamsize each time tokenize_bytes ran, and then this was checked in the PUSH_CHAR macro. However, there is one other place in the file where function make_stream_space() is called (in end_line()), and when this happens self->stream_cap is increased but maxstreamsize is not updated, making the check incorrect. In rare circumstances (see original issue or test case) this could cause a crash. The resolution is to just check self->stream_cap directly. Author: Jeff Carey <[email protected]> Closes pandas-dev#15195 from jeffcarey/fix/14125 and squashes the following commits: d3c5f28 [Jeff Carey] BUG: Fixed incorrect stream size check (pandas-dev#14125)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's the code (input data is at the end of this message):
It fails with:
Small perturbations of the input file (adding or removing characters) makes it work, as does
engine='python'
. Note that while one row (or more) of the file contains "extra" columns, I have only asked Pandas to read column 0, which it should well be able to do since that column has a consistent, short length.INSTALLED VERSIONS
commit: None
python: 3.5.2.final.0
python-bits: 64
OS: Linux
OS-release: 3.13.0-85-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
pandas: 0.18.1
nose: None
pip: 8.1.2
setuptools: 25.1.6
Cython: 0.24.1
numpy: 1.11.1
DATA
The text was updated successfully, but these errors were encountered: