Skip to content

read_table, header flag. false interpreted as 0. #6113

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

Closed
cyrusmaher opened this issue Jan 27, 2014 · 5 comments · Fixed by #11182
Closed

read_table, header flag. false interpreted as 0. #6113

cyrusmaher opened this issue Jan 27, 2014 · 5 comments · Fixed by #11182
Labels
API Design IO CSV read_csv, to_csv
Milestone

Comments

@cyrusmaher
Copy link
Contributor

For read_table, Would it be possible to make "header=None" and "header=False" have the same behavior? Interpreting "False" as saying that the first line is the header has tricked me a couple times...

@ghost
Copy link

ghost commented Jan 27, 2014

You might have a good point but we can't break that much code without a stronger reason.

Sorry, that's what maintaining a library that has lots of users and existing code is like.

@ghost ghost closed this as completed Jan 27, 2014
@ghost ghost reopened this Jan 27, 2014
@ghost
Copy link

ghost commented Jan 27, 2014

I spoke too soon. The docstring leaves that behavior undefined and what you suggest makes sense.
We'll talk this over for 0.14.0. I think we can do this.

A the very least, raising on bool with a reasonable error message will
eliminate the hazard and not cause much pain for existing code that relies
on undocumented behavior.

@cyrusmaher
Copy link
Contributor Author

Perfect. If you guys could do it sooner, all the better. In R's read.table, header=False gives pandas' header=None behavior. With the pitfalls of language slurring added to the fine False/None distinction, my feeling is raising an error will cut down on unintended behavior with comparatively little inconvenience...

@ghost
Copy link

ghost commented Jan 27, 2014

That's been there for a while. I don't think there's any time pressure.
our next release is a bugfix release and this could conceivably break
someone's ill-written code. It'll wait till 0.14.0. You're welcome to use master
before 0.14.0 is actually released. It's usually perfectly usable.

If we don't sort this within a month or so, ping us.

@cyrusmaher
Copy link
Contributor Author

Sounds good. Thanks for taking a look!

On Sun, Jan 26, 2014 at 9:05 PM, y-p [email protected] wrote:

That's been there for a while. I don't think there's any time pressure.
our next release is a bugfix release and this could conceivably break
someone ill-written code. It'll wait till 0.14.0. You're welcome to use
master
before 0.14.0 is actually released. It's usually perfectly usable.

If we don't sort this within a month or so, ping us.


Reply to this email directly or view it on GitHubhttps://github.com//issues/6113#issuecomment-33342316
.

@jreback jreback modified the milestones: 0.15.0, 0.14.0 Apr 9, 2014
@jreback jreback added the CSV label Apr 9, 2014
@jreback jreback modified the milestones: 0.16.0, Next Major Release Mar 3, 2015
@jreback jreback modified the milestones: 0.17.0, Next Major Release Sep 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Design IO CSV read_csv, to_csv
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants