Inline table support

[Jenselme]

When I try to parse a file that contains an inline table (as defined by toml 0.4, the parser crashes. For intance, with:

origins_to_ranks = {nomderue = 20, communes = 10}

I get.

  File "/home/jenselme/Stage3A/geo-api3/chsdi/tests/functional/test_sphinx.py", line 26, in test_sphinx_api_query
    config = toml.load(config_file)
  File "/home/jenselme/Stage3A/geo-api3/.venv/lib/python3.4/site-packages/toml.py", line 43, in load
    return loads(f.read(), _dict)
  File "/home/jenselme/Stage3A/geo-api3/.venv/lib/python3.4/site-packages/toml.py", line 331, in loads
    value, vtype = load_value(pair[1])
  File "/home/jenselme/Stage3A/geo-api3/.venv/lib/python3.4/site-packages/toml.py", line 453, in load_value
    parsed_date = load_date(v)
  File "/home/jenselme/Stage3A/geo-api3/.venv/lib/python3.4/site-packages/toml.py", line 350, in load_date
    tz = TomlTz(val[19:24])
  File "/home/jenselme/Stage3A/geo-api3/.venv/lib/python3.4/site-packages/toml.py", line 9, in __new__
    self._hours = int(toml_offset[:3])
ValueError: invalid literal for int() with base 10: 'omm'

Can you add support for this syntax please?

[oconnor663]

Ran into this issue myself. toml is failing to parse this example from the spec:

points = [ { x = 1, y = 2, z = 3 },
           { x = 7, y = 8, z = 9 },
           { x = 2, y = 4, z = 8 } ]

[ldav1s]

I ran into this too. I was able work around it by reformulating the inline tables as an array of tables which worked.

[Jenselme]

Can we have a new release with the support for inline table?

[Jenselme]

@uiri Any plans on doing a new release to pypi with inline objects support?

[uiri]

Assuming no further issues nor pull requests present themselves in the mean time, I plan on doing a new release once the timezone issue and the current pull requests are resolved.