Issue 1447141
Created on 2006-03-10 11:04 by schlatterbeck, last changed 2006-03-10 11:04 by schlatterbeck.
|
| File name |
Uploaded |
Description |
Edit |
Remove |
|
export-tb.txt
|
schlatterbeck,
2006-03-10 11:04
|
traceback |
|
|
|
patch-date
|
schlatterbeck,
2006-03-10 12:09
|
Fix for date-parsing, allow single digit in seconds |
|
|
|
| msg2227 |
Author: [hidden] (schlatterbeck) |
Date: 2006-03-10 11:04 |
|
See attached traceback.
|
| msg2228 |
Author: [hidden] (schlatterbeck) |
Date: 2006-03-10 11:14 |
|
Logged In: YES
user_id=34818
The offending date (Just added a print statement in
roundup/date.py) is 2006-02-15.00:00:0.000 -- looks like
postgres returns a wrong date here??
Maybe I should mention that I'm using postgresql backend.
Roundup 0.8 was more tolerant:
>>> from roundup.date import Date
>>> Date ('2006-02-15.00:00:0.000')
2006-02-15.00:00:0.000
Traceback (most recent call last):
...
>>> from roundup08.date import Date
>>> Date ('2006-02-15.00:00:0.000')
<Date 2006-02-15.00:00:0.000000>
|
| msg2229 |
Author: [hidden] (schlatterbeck) |
Date: 2006-03-10 12:09 |
|
Logged In: YES
user_id=34818
See attached patch. I've changed the regex to allow a single
digit in seconds.
|
|
| Date |
User |
Action |
Args |
| 2006-03-10 11:04:19 | schlatterbeck | create | |
|