Modify ↓
Ticket #7436 (closed defect: duplicate)
Opened 4 years ago
Last modified 4 years ago
ValueError: not a known date format.
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description (last modified by eblot) (diff)
Python Traceback
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
resp = chosen_handler.process_request(req)
File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev-py2.4.egg/webadmin/web_ui.py", line 119, in process_request
path_info)
File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev-py2.4.egg/webadmin/ticket.py", line 163, in process_admin_request
mil.due = util.parse_date(req.args.get('duedate'))
File "/usr/lib/python2.4/site-packages/trac/util/datefmt.py", line 114, in parse_date
raise ValueError, '%s is not a known date format.' % text
ValueError: 081308 is not a known date format.
Attachments
Change History
comment:1 Changed 4 years ago by osimons
- Resolution set to duplicate
- Status changed from new to closed
comment:2 Changed 4 years ago by eblot
- Description modified (diff)
... or you did not used the format that is specified as a hint along with the date field.
Please also take care of defining a meaningful ticket summary when you report an issue, as specified in the NewTicketGuidelines, quoting: Provide a concise and precise Summary. As when you write an e-mail, the ticket's summary is the first thing people will see about this ticket, in the timeline, reports and other places in Trac, so it's quite important to get it right.
comment:3 Changed 4 years ago by eblot
- Summary changed from Traceback (most recent call last): to ValueError: not a known date format.
Note: See
TracTickets for help on using
tickets.



If you had searched for 'ValueError parse_date' or similar, you'd have noticed a number of pre-existing tickets... You seem to be running an older version of Trac as this has been fixed for 0.11 - see #4927.