You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
python-toml 0.9.6 doesn't support hex/octal/bin integer value although link to TOML 0.5.0 was bumped (a444a36#diff-88b99bb28683bd5b7e3a204826ead112).
BurntSushi/toml-test doesn't have tests for TOML v0.5.0 see toml-lang/toml-test#49 so it's not clear why python-toml is considered to support TOML 0.5.0
[vlotorev@host ~]$ python3 -c "import toml; toml.loads('a=0x1')"
Traceback (most recent call last):
File "/home/vlotorev/.local/lib/python3.4/site-packages/toml.py", line 400, in loads
multibackslash)
File "/home/vlotorev/.local/lib/python3.4/site-packages/toml.py", line 516, in _load_line
raise ValueError("Invalid date or number")
ValueError: Invalid date or number
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/vlotorev/.local/lib/python3.4/site-packages/toml.py", line 402, in loads
raise TomlDecodeError(str(err))
toml.TomlDecodeError: Invalid date or number
the same error fires for 'a=0b1' and 'a=0o1'.
Note:
The text was updated successfully, but these errors were encountered:
TOML v0.5.0 supports hex/octal/bin integer values: https://github.com/toml-lang/toml#integer (TOML v0.4.0 doesn't support these).
python-toml 0.9.6 doesn't support hex/octal/bin integer value although link to TOML 0.5.0 was bumped (a444a36#diff-88b99bb28683bd5b7e3a204826ead112).
BurntSushi/toml-test doesn't have tests for TOML v0.5.0 see toml-lang/toml-test#49 so it's not clear why python-toml is considered to support TOML 0.5.0
the same error fires for 'a=0b1' and 'a=0o1'.
Note:
The text was updated successfully, but these errors were encountered: