Whole file
bastikr/boolean.py
The author described this change as “Fix bug in DualBase.eval”. It counts as a record because the check below fails on the code as it stood at fff7e785c and passes on f10cb6a2d, with nothing else changed between the two runs.
Projectbastikr/boolean.py
Fix saved2012-06-05
Sharing licenceBSD-2-Clause · LICENSE.txt
Change size+2 −0
What the code was meant to do, written into the code itself as a save note
Fix bug in DualBase.eval
The change
| 756 | 756 | if ai in aj.args or\ | |
| 757 | 757 | (isdual and all(arg in aj.args for arg in ai.args)): | |
| 758 | 758 | del args[j] | |
| 759 | + | if i >= len(args): | |
| 760 | + | break | |
| 759 | 761 | elif isdual: | |
| 760 | 762 | negated = None | |
| 761 | 763 | for arg in ai.args: |
The check that tells the two apart
fail→pass·boolean/test_boolean.py::DualBaseTestCase::test_eval
Check file boolean/test_boolean.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 itfff7e785c3c7ba6888ac48bc444cc460e709ee03
Broken version dated2011-12-09
Moduleboolean.boolean
Units changedDualBase
Fingerprint392a545cc831c2fb
Checked2026-08-18 by goldset/0.1
Every field above is generated by our program. None of it is written by hand.