Bug #278: Incorrect fuzzy date parsing.#279
Closed
shmuga wants to merge 1 commit into
Closed
Conversation
* Added test case to bug. * Fix bug when first part of ymd object is larger than 12 and length of ymd array == 2 - it's exactly date not month. * Added rule for case when date in format "DD.MM" or "MM.DD"
| def testFuzzyWithDotNotation(self): | ||
| s1 = "27.08" | ||
| today_year = date.today().year | ||
| self.assertEqual(parse(s1, fuzzy=True), datetime(today_year, 8, 27, 0, 0)) |
Member
There was a problem hiding this comment.
This should be changed in the following ways:
- Just pass a specific date to
defaultso you don't have to worry about retrieving the current year - Remove the
fuzzykeyword. It is unnecessary.
Member
|
Doesn't seem like this is still being worked on, closing this. |
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
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.
Bug related to #278.