feat: replace python-dateutil with dateparser for natural language support#33
Open
feat: replace python-dateutil with dateparser for natural language support#33
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…pport dateparser understands "yesterday", "3 hours ago", "Friday", etc. that dateutil.parser does not. The +offset and "now" special cases handled before the parser call are preserved unchanged. In _parse_timespec the dateutil.parser.ParserError catch is replaced with ValueError (dateparser returns None on failure rather than raising, and _parse_dt now raises ValueError in that case). Adds TestNaturalLanguage tests covering yesterday, today, relative hours, day names, and invalid input. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
python-dateutildependency withdateparserdateparserunderstands natural language input thatdateutil.parserdoes not:"yesterday","3 hours ago","Friday","last week", etc.+offsetand"now"special cases handled before the parser call are preserved unchangeddateutil.parser.ParserErrorcatch in_parse_timespecreplaced withValueError(dateparser returnsNoneon failure rather than raising;_parse_dtnow raisesValueErrorin that case)Motivation
dateutil.parser.parse("yesterday")raises aParserError. This means users cannot write things likeplann select --from yesterday— they have to spell out the ISO date.dateparserhandles this family of inputs out of the box.Test plan
tests/test_timespec.pytests pass (29 passed, 1 skipped)TestNaturalLanguagetests added covering:yesterday,today,3 hours ago, day name, invalid input