Skip to content
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

fix problem with date format 02.01.2006 #133

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mehanizm
Copy link

@mehanizm mehanizm commented Aug 6, 2021

I've fixed the errors with date formats with the leading date: 02.01.2006, 02/01/2006.
Without fix the ParseAny function was returning the error "month out of range".

Tests were added.

@taalhach
Copy link

@araddon any possibility of merging this PR in master. i am working with dates that are in this format

@vryazanov
Copy link

@araddon any plans to merge it?

@alhamsya
Copy link

@araddon any plans to merge it ?

dron22 pushed a commit to dcmn-com/dateparse that referenced this pull request May 8, 2023
This is a commit from https://github.com/mehanizm/dateparse/tree/fix_02.01.2006
which attempts to fix the limitation with day first date formats. It was not
yet merged into the original repo (araddon#133)
klondikedragon added a commit to itlightning/dateparse that referenced this pull request Dec 12, 2023
Incorporates PR araddon#133 from https://github.com/mehanizm to fix araddon#129

Adds test cases to verify the following are already fixed:
* araddon#105
iTanken added a commit to godoes/dateparse that referenced this pull request Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants