arrow-py / arrow-py/arrow

Updated to latest, string unix timestamp is not understood by 'get'

Open
#1,117 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
9.1k
Forks
784
PR merge metrics
No merged PRs in 30d

Description

## Issue Description

```python
import arrow

arrow.get('1657831049')
```
results in
```
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

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue with arrow.get('1657831049') on Arrow 1.2.2, then trace the parsing path used by arrow.get and review its existing parser tests. Done means string Unix timestamps are accepted while the listed date formats continue to parse correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.