'mktime' error when setting milestone due date

[trac@…]

Editing a milestone using the web interface, Setting the due date to '12/31/59' produces the following error message...

---

Oops...
Trac detected an internal error: 
mktime argument out of range

Python traceback
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/modpython_frontend.py", line 206, in handler
    dispatch_request(mpr.path_info, mpr, env)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/trac/ticket/roadmap.py", line 355, in process_request
    self._do_save(req, db, milestone)
  File "/usr/lib/python2.4/site-packages/trac/ticket/roadmap.py", line 393, in _do_save
    milestone.due = due and parse_date(due) or 0
  File "/usr/lib/python2.4/site-packages/trac/util.py", line 453, in parse_date
    seconds = time.mktime(date)
 !OverflowError: mktime argument out of range

[cboos]

Did you mean year 1959 or 2059? Both are not in the range anyway ;)

With the source:sandbox/datetime branch, we will probably be able to handle a wider range of dates.

[trac@…]

Replying to cboos:

Did you mean year 1959 or 2059?

I was wanting 2059, but it only allows a 2-digit date to be entered.

(ps.Thanks for all your hard work on Trac.. great product, I love using it :))

[osimons <simon-code@…>]

This is likely the same issue as #5322 - but as it was before the 0.11 datetime-everywhere merge.

Let's focus on the newer ticket, and closing this one as duplicate.

[cboos]

(clearing milestone field, as it's a duplicate; besides not applicable is for valid issues that can't be tied to a specific release for some reason: plugin, project issue, etc.)