Modify ↓
Opened 19 years ago
Closed 19 years ago
#5098 closed enhancement (wontfix)
4/1/7 ought to be a valid date format
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.3.1 |
| Severity: | normal | Keywords: | date format |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
When I created a milestone with date "4/1/7", I got the following:
Traceback (most recent call last):
File "/data/devjavu/releases/20070406070414/trac/lib/trac/web/main.py", line 387, in dispatch_request
dispatcher.dispatch(req)
File "/data/devjavu/releases/20070406070414/trac/lib/trac/web/main.py", line 237, in dispatch
resp = chosen_handler.process_request(req)
File "/tmp/bdist/webadmin/web_ui.py", line 109, in process_request
File "/tmp/bdist/webadmin/ticket.py", line 163, in process_admin_request
File "/data/devjavu/releases/20070406070414/trac/lib/trac/util/datefmt.py", line 114, in parse_date
raise ValueError, '%s is not a known date format.' % text
ValueError: 4/1/7 is not a known date format.
Attachments (0)
Change History (3)
comment:1 by , 19 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | none |
comment:2 by , 19 years ago
comment:3 by , 19 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Yes, as eblot said you need to use a 2-digit year, which is standard for date formatting.
Note:
See TracTickets
for help on using tickets.



Actually, a "valid" date would be 4/1/07.
Non-ISO8601 dates are parsed with the regular Python date parser, which does not seem to accept years coded on a single digit.
Propose as wontfix.