This was brought up in the community call.
#50939 adds support for mixed ISO8601 strings. But people may have mixed not-necessarily-ISO8601 strings, and want them parsed in a more performant manner than apply.
So, format='mixed' could accomplish that. This would risk parsing ['12/01/2000', '13/01/2000'] in different formats, but because users have to opt-in to it by explicitly writing format='mixed', then it should be clear to them that they will need to accept whatever risks come from this. In any case, they can always use dayfirst.
Alternatives would be to add a new keyword argument, or un-deprecate infer_datetime_format and change its behaviour. However:
infer_datetime_format but changing behaviour might be confusingDocs and error messages should be updated to direct users towards this option
It's probably easiest to tackle this as part of #50939
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4