Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
pandas.read_excel index_col argument behavior seems to be wrong (or unexpected, as by the docs)
See original GitHub issuehttp://pandas.pydata.org/pandas-docs/stable/generated/pandas.read_excel.html#pandas.read_excel
It’s about the parameter index_col.
From the docs, I read
index_col : int, list of ints, default None
Column (0-indexed) to use as the row labels of the DataFrame. Pass None if there is no such column. If a list is passed, those columns will be combined into a MultiIndex"
I use the function with args={index_col=3, parse_cols=“D-J”} (so it should parse from column 3 to column 9 included, 0-indexed). And I expected D to be used as Index, but actually it was column G. I am not sure if it is the expected behavior, if then, maybe argument order should be changed to show that index_col depends on parsed_cols.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’d expand the explanation of
index_colin theread_exceldocstring here https://github.com/pandas-dev/pandas/blob/697d0269aa6903be75db97afb45f9976abd2406d/pandas/io/excel.py#L85And them maybe add an example to the narrative docs, somewhere around here http://pandas.pydata.org/pandas-docs/stable/io.html#parsing-specific-columns
(by changing this file): https://github.com/pandas-dev/pandas/blob/697d0269aa6903be75db97afb45f9976abd2406d/doc/source/io.rst
@chris-b1 I shall work on it. But I’m more interested in some coding issue. Could you suggest some for starters?