Repository navigation
Remove the Python divergence entries closed by idfkit#183 - #47
Merged
Merged
Conversation
idfkit no longer stores a blank fixed field as "" (idfkit#183, idfkit#242), so the model agrees with write_idf and write_epjson and a re-parse of its own IDF output equals the original. The python round-trip entries for numeric-zero-against-blank and positional-trailing-unset-no-extensible are therefore stale and are removed, together with the positional section they leave empty. The register now holds 10 entries over 5 issues and 7 cases, 5 against python and 5 against typescript. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEegXpWqwRPaofngRx6L3h
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
idfkit no longer stores a blank fixed field as
""(idfkit/idfkit#183, fixed in idfkit/idfkit#242). The model now agrees withwrite_idfandwrite_epjson, so re-parsing idfkit's own IDF output equals the original. That makes twopython/round-tripentries stale:numeric-zero-against-blankpositional-trailing-unset-no-extensibleThis removes both, along with the
positionalsection header they leave empty, and recounts the register header. The register now holds 10 entries over 5 issues and 7 cases: 5 against python, 5 against typescript. No typescript entry changes.Verification
python -m pytest runners/tests: 229 passed.python runners/run.py --library <idfkit>against this branch, where<idfkit>is a scratch merge of idfkit#236 (IDFObject.update) and idfkit#242: PASS, exit 0. 74 cases, 226 assertions: 218 passed, 5 failed, all 5 of them outstanding exceptions (#186, #187). No stale entries and no unexpected failures. The idfkit unit suite passes on the same merge.updatecases, which needIDFObject.updatefrom idfkit#236.After merge
Cut
conformance-2026.20on the merge commit. idfkit#242 then sets[tool.idfkit.conformance] levelto it. Because levels fromconformance-2026.17on include theupdatecases, #242 adopts the new level once idfkit#236 has landed on idfkit main.Per CODEOWNERS (FR-067), a change to the register needs review from a maintainer of the other language.
Generated by Claude Code