Fixes time parsing, closes #32

This commit is contained in:
Manuel Ebert 2012-05-24 18:14:12 +02:00
parent 7b0829121f
commit 9a9a80cd8e
2 changed files with 8 additions and 0 deletions

View file

@ -3,6 +3,7 @@ Changelog
### 0.2.4 (May 24, 2012) ### 0.2.4 (May 24, 2012)
* [Fixed] Dates such as "May 3" will now be interpreted as being in the past if the current day is at least 28 days in the future
* [Fixed] Bug where composed entry is lost when the journal file fails to load * [Fixed] Bug where composed entry is lost when the journal file fails to load
* [Changed] Changed directory structure and install scripts (removing the necessity to make an alias from `jrnl` to `jrnl.py`) * [Changed] Changed directory structure and install scripts (removing the necessity to make an alias from `jrnl` to `jrnl.py`)

View file

@ -241,6 +241,13 @@ class Journal:
else: else:
date = datetime(*date[:6]) date = datetime(*date[:6])
# Ugly heuristic: if the date is more than 4 weeks in the future, we got the year wrong.
# Rather then this, we would like to see parsedatetime patched so we can tell it to prefer
# past dates
dt = datetime.now() - date
if dt.days < -28:
date = date.replace(date.year - 1)
return date return date
def new_entry(self, raw, date=None): def new_entry(self, raw, date=None):