Whole file

uiri/toml

The author described this change as Raise an exception if EOF is reached and a string is unterminated. It counts as a record because the check below fails on the code as it stood at f4f0b84fd and passes on 543091066, with nothing else changed between the two runs.

Projectuiri/toml
Fix saved2020-04-22
Sharing licenceMIT · LICENSE
Change size+3 0

What the code was meant to do, written into the code itself as a save note

Raise an exception if EOF is reached and a string is unterminated

The change

358358 if keyname:
359359 raise TomlDecodeError("Key name found without value."
360360 " Reached end of file.", original, len(s))
361+ if openstring: # reached EOF and have an unterminated string
362+ raise TomlDecodeError("Unterminated string found."
363+ " Reached end of file.", original, len(s))
361364 s = ''.join(sl)
362365 s = s.split('\n')
363366 multikey = None

The check that tells the two apart

failpass·tests/test_api.py::test_unterminated_string_eof[opt

Check file tests/test_api.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.

Origin and history

The code before itf4f0b84fd84265b296312153628cd9dbd5961664
Broken version dated2020-01-03
Moduletoml.decoder
Units changedloads
Fingerprint6b715c5f7815fbd6
Checked2026-08-18 by goldset/0.1

Every field above is generated by our program. None of it is written by hand.

Other bugs found in uiri/toml