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.

Sign up for GitHub

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

Jump to bottom

Bug when integrating data that 'looks like a date' #296

Closed

mboudet opened this issue Oct 27, 2021 · 0 comments · Fixed by #297

Contributor

mboudet commented Oct 27, 2021

Example : 'St18-208' is recognized as a date, but wrongly formatted.

It raises 'calendar.IllegalMonthError' instead of 'parser.ParserError', so we do not catch it.

We should not try to blanket convert all values to date. Maybe only for CSV, and explicitely specified 'date' columns?
Should catch anything that comes instead of ParserError.

mboudet mentioned this issue

Merged

mboudet closed this as completed in #297

mboudet added a commit that referenced this issue


          Fix #296 (#297)

8859bc1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment