You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
arrow.parser.ParserError: Could not match input '1657831049' to any of the following formats: YYYY-MM-DD, YYYY-M-DD, YYYY-M-D, YYYY/MM/DD, YYYY/M/DD, YYYY/M/D, YYYY.MM.DD, YYYY.M.DD, YYYY.M.D, YYYYMMDD, YYYY-DDDD, YYYYDDDD, YYYY-MM, YYYY/MM, YYYY.MM, YYYY, W.
worked beforehand but with the latest version it does not.
We would like to accept a lot of time formats and some of them are strings some of them are unix timestamps, so forcing a int/float conversion is unacceptable. It would be nice to use string unix timestamps.
System Info
🖥 OS name and version: ubuntu
🐍 Python version: 3.8
🏹 Arrow version: 1.2.2
The text was updated successfully, but these errors were encountered:
sebtrack
changed the title
Updated to latest string unix timestamp is not understood by 'get'
Updated to latest, string unix timestamp is not understood by 'get'
Jul 14, 2022
From reading the release history, this behavior was intentionally changed in version 0.15.0 "to support the ISO 8601 basic format and to address bugs such as #447". Is this really something that people would want to revert?
Issue Description
results in
worked beforehand but with the latest version it does not.
We would like to accept a lot of time formats and some of them are strings some of them are unix timestamps, so forcing a int/float conversion is unacceptable. It would be nice to use string unix timestamps.
System Info
The text was updated successfully, but these errors were encountered: