-
Notifications
You must be signed in to change notification settings - Fork 5
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
Allow to disable skipping empty rows/columns at the beginning of the worksheet #209
Comments
That being said we could add a parameter similar to |
In an ETL pipeline incoming Excel files use arbitrary layout (inluding multi-rows headers and/or empty rows between header and the data). The task is to process the files using predefined specs for |
This requires changes on calamine side. I will try to open a PR soon. Since 0.11 has some nice improvements, we don't want to postpone it even more for that |
I'm afraid I'm facing the same issue. Our systems are currently using Whats's the use case: In one of our systems, users specified a row index in their Excel sheet that is of special interest. But we cannot just start reading from that row (with Hence, for moving to |
There is a similar issue, which is closed without, as it appears, any fix (with v
0.9.1
being actual).Expected behaviour is outlined in examples of
python-calamine
for an optionskip_empty_area
:This automatic behavior is kind of surprising when dealing with files with empty parts at the beginning, as the whole rows calculations get confusing. i.e. for
header_row
you have to count rows as they appear (i.e. including empty rows), but forskip_rows
you have to count as if there are no empty rows, which is clearly not the most user-friendly approach.Please consider adding an option/parameter to disable default behavor.
Thank you!
The text was updated successfully, but these errors were encountered: