scrapinghub / scrapinghub/dateparser

Parser returns None for "Sep 30 2025"

Open
#1,282 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2.9k
Forks
520
Avg merge
22h 56m
Merged PRs (30d)
6

Description

Version:

dateparser = "1.2.2"

How to reproduce:

import dateparser

dateparser.parse(date_string="Sep 30 2025")

dateparser.parse(date_string="Sep 30 2025", languages=["en"],)

dateparser.parse(date_string="Sep 30 2025", languages=["en"], region="US",)

For other months it works fine:

In [7]: dateparser.parse(date_string="Jan 30 2025")
Out[7]: datetime.datetime(2025, 1, 30, 0, 0)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported dateparser.parse examples on version 1.2.2 and compare the September result with the working January case. Trace the parsing path for month names, then verify that the three reported calls return the expected datetime for "Sep 30 2025" without regressing other months.

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
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.