Commit bd9badf2 authored by Jérome Perrin's avatar Jérome Perrin

tidrange proto: disable unsupported inputs

parent 025d4914
...@@ -42,4 +42,13 @@ ERROR timespec: 06.05.2009 expected time: 2009-05-06T00:00:00Z parsed time: 2009 ...@@ -42,4 +42,13 @@ ERROR timespec: 06.05.2009 expected time: 2009-05-06T00:00:00Z parsed time: 2009
ERROR timespec: Jun 6, 5AM expected time: 2009-06-06T05:00:00Z parsed time: 0000-06-06T00:00:05Z ERROR timespec: Jun 6, 5AM expected time: 2009-06-06T05:00:00Z parsed time: 0000-06-06T00:00:05Z
ERROR timespec: 5AM Jun 6 expected time: 2009-06-06T05:00:00Z parsed time: 0000-06-01T00:00:05Z ERROR timespec: 5AM Jun 6 expected time: 2009-06-06T05:00:00Z parsed time: 0000-06-01T00:00:05Z
``` ```
\ No newline at end of file
# after disabling unsupported inputs
```
python prototype/proto.py
go run prototype/proto.go
```
no more errors reported.
...@@ -31,13 +31,18 @@ ...@@ -31,13 +31,18 @@
# this input is "ambiguous" # this input is "ambiguous"
# 2009-08-29T12:00:00Z 10am noon # 2009-08-29T12:00:00Z 10am noon
2009-08-25T19:20:00Z last tuesday # not supported by date parser
2009-07-05T00:00:00Z July 5th # 2009-08-25T19:20:00Z last tuesday
# non consistent behavior ( go keep current hour:minutes - python use midnight )
# 2009-07-05T00:00:00Z July 5th
2009-06-05T00:00:00Z 06/05/2009 2009-06-05T00:00:00Z 06/05/2009
2009-05-06T00:00:00Z 06.05.2009 # parsed as month/day (at least for me ... it might depend on some locales ?)
#2009-05-06T00:00:00Z 06.05.2009
2009-06-06T05:00:00Z Jun 6, 5AM # go parser is wrong on this one
2009-06-06T05:00:00Z 5AM Jun 6 # 2009-06-06T05:00:00Z Jun 6, 5AM
# go parser is wrong on this one
# 2009-06-06T05:00:00Z 5AM Jun 6
2009-06-07T06:00:00Z 6AM, June 7, 2009 2009-06-07T06:00:00Z 6AM, June 7, 2009
2008-12-01T00:00:00Z 2008-12-01 2008-12-01T00:00:00Z 2008-12-01
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment