Rel implicitly converted to UTC

[sjlongland]

I noticed this taking a JSON grid from the WideSky API server system tests, loading it in and dumping it out in ZINC format for documentation purposes…

if I create a file grid.json:

{
  "meta": {
    "ver": "2.0",
    "hisEnd": "t:2016-01-01T00:00:00-00:00 Rel",
    "hisStart": "t:2016-01-01T00:00:00-00:00 Rel"
  },
  "cols": [
    {
      "name": "ts"
    },
    {
      "name": "v0",
      "id": "r:00000111-0000-0000-0000-000000000000"
    },
    {
      "name": "v1",
      "id": "r:00000112-0000-0000-0000-000000000000"
    }
  ],
  "rows": [
    {
      "ts": "t:2016-01-01T00:00:00-00:00 Rel",
      "v0": "n:1 Wh",
      "v1": "n:1 Wh"
    }
  ]
}

then in a Python shell:

import hszinc

grid = hszinc.parse(open('grid.json','r').read(), mode=hszinc.MODE_JSON)
open('grid.zinc','w').write(hszinc.dump(grid, mode=HSZINC.MODE_ZINC))

I get this output:

ver:"2.0" hisEnd:2016-01-01T00:00:00+00:00 UTC hisStart:2016-01-01T00:00:00+00:00 UTC
ts,v0 id:@00000111-0000-0000-0000-000000000000,v1 id:@00000112-0000-0000-0000-000000000000
2016-01-01T00:00:00+00:00 UTC,1.0Wh,1.0Wh

Those DateTime literals should remain in the Rel time-zone.