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

find_dates fails when there's a number after a date #199

Open
alexmadey-oc opened this issue Mar 18, 2024 · 1 comment
Open

find_dates fails when there's a number after a date #199

alexmadey-oc opened this issue Mar 18, 2024 · 1 comment

Comments

@alexmadey-oc
Copy link

The following fails to find any dates datefinder.find_dates("9/15/27 144A"). I think datefinder wants to treat the 144A as an hour component, but it fails since 144A is not a valid hour. If I put a valid hour like "9/15/27 12", it parses the 12 as an hour component. A potential solution would be to allow the user to specify that they only want to find dates and not any time components.

@Diglador
Copy link

06-15 21:21:51.754 5395 5395
2024-06-15 21:21:51.754 5395 5395
same problem

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

No branches or pull requests

2 participants