-
Notifications
You must be signed in to change notification settings - Fork 32
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
type casting assumes 'month first' for ambiguous dates #16
Comments
Good point. In fact, the date format detection could be implemented in a way similar to that of type detection. I.e., test dates record by record until a given confidence threshold has been crossed. |
To clarify, |
* fixes: Bump to version 0.43.0 [FIX] Misc compatibility fixes Be explicit with kwarg [ENH] Loosen up dev requirements [DOC] Show a csv dialect example (closes #22) [NEW] Add `whitelist` option to remove_keys [ENH] Add prettify command and use it! [ENH] Pass kwargs to date parser (closes #16) Fix incorrect int parsing during is_numeric checks
💯 |
Right now, the type detection does infer a date, datetime or time types without taking into account the fact that
01/02/2002
can be both Februrary the 1st or January the 2nd depending on the date format used respectivelyDD/MM/YYYY
andMM/DD/YYYY
.This might be undecidable in some rare cases, but in general it's possible given enough values to decide between both formats.
One possible way, to handle this in
meza
is to use a higher level datatype for representing the type of a field to replace the current string representation. For instance:Basically, use a representation that takes optional extra information about the type.
The text was updated successfully, but these errors were encountered: