Why Is the Migration to Python 3 Taking So Long?

Re:Why Is the Migration to Python 3 Taking So Long? by oarabbus_ on Thursday November 14, 2019 @05:38PM (#21540279)

I ran into an issue recently specific to Pandas and python3 with unicode.

pd.read_excel(filepath) will read an entire dataset even if it contains unicode characters.

pd.ExcelFile() silently drops(!!) unicode rows. The resulting object will simply skip unicode-containing rows (in ANY column) them without even a warning.

For example, if you had an excel file:

word

---

"hello"

你早

"hello"

then pd.read_excel() would give you a dataframe with 5 rows. ExcelFile() on the other hand would return (silently!) a dataframe with only the first two and the last row.

Maybe this is a pandas issue, not a python issue, but it was really horrendous to debug for such a long time only to realize this was the issue.

[ Parent | on HN ]

Re:Why Is the Migration to Python 3 Taking So Long? by j88439h84 on Thursday November 14, 2019 @08:16PM (#21541391)

Is there an issue for this in the bug tracker?

[ Parent | on HN ]

Re:Why Is the Migration to Python 3 Taking So Long? by oarabbus_ on Friday November 15, 2019 @03:24AM (#21543213)

I searched, and this is the closest thing (https://github.com/pandas-dev/pandas/issues/11503) but it is not the issue I experienced.

I'm not sure how to submit a bug report, to be honest.

[ Parent | on HN ]