One function
UdaExecConfig in teradata/PyTd
The author described this change as “Fix for #16”. It counts as a record because the checks below fail on the code as it stood at bb4a74820 and pass on 51d7f6e98, with nothing else changed between the two runs.
Projectteradata/PyTd
Fix saved2015-10-05
Sharing licenceMIT · LICENSE.txt
Change size+1 −0
What the code was meant to do, written into the code itself as a docstring
UdaExec configuration loader and resolver.
The change
| 65 | 65 | else: | |
| 66 | 66 | value = value.replace("$$", "$") | |
| 67 | 67 | error = None | |
| 68 | + | break | |
| 68 | 69 | except KeyError as e: | |
| 69 | 70 | error = e | |
| 70 | 71 | if error is not None: |
The check that tells the two apart
fail→pass·test/test_udaexec_config.py::UdaExecConfigTest::testConfigEscapeCharacter
fail→pass·test/test_udaexec_config.py::UdaExecConfigTest::testExcapeCharacterInDataSource
Check file test/test_udaexec_config.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 itbb4a748200409b62552c00f97a5da68e7e59bc9e
Broken version dated2015-08-26
Moduleteradata.udaexec
Units changedUdaExecConfig
Fingerprint4031dacf82139d94
Checked2026-08-18 by goldset/0.1
Every field above is generated by our program. None of it is written by hand.