Skip to content

DOC: fix some doc errors/warnings #9643

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

Merged
merged 1 commit into from
Mar 14, 2015

Conversation

jorisvandenbossche
Copy link
Member

  • pd.read_csv('tmp2.sv', sep=None) was given the warning "ParserWarning: Falling back to the 'python' engine because the 'c' engine does not support sep=None with delim_whitespace=False; you can avoid this warning by specifying engine='python'"
    Is this correct? (assuming so I just added what the warning message was saying)
  • with the ordered -> unordered change in the Categoricals, the example on comparing them was failing (see http://pandas-docs.github.io/pandas-docs-travis/categorical.html#comparisons)

@jorisvandenbossche jorisvandenbossche added this to the 0.16.0 milestone Mar 13, 2015
@jreback
Copy link
Contributor

jreback commented Mar 13, 2015

sep=None should default back to sniffing mode, which IIRC is only in engine='python'. So I think this is correct.

Maybe create an issue to investigate this and see if it really should show the warning and/or should implement in c engine (this just involved using the sniffer so it should be just a bit of pre-processing)

@jorisvandenbossche
Copy link
Member Author

This warning was already there in previous pandas releases, it was just not in the docs because the example was incorrect there (I fixed it recently). But indeed, let's open an issue to see if this could be added to the c engine.

@jorisvandenbossche
Copy link
Member Author

Opened an issue here: #9645

jorisvandenbossche added a commit that referenced this pull request Mar 14, 2015
DOC: fix some doc errors/warnings
@jorisvandenbossche jorisvandenbossche merged commit 8f422e2 into pandas-dev:master Mar 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants