Fix Symbol.ranges unpacking #30
Merged
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.
The Symbol.ranges attribute in kconfiglib returns 4-tuples (low, high, cond, loc), but menuconfig and guiconfig were using the old 3-tuple unpacking pattern, causing ValueError when processing integer/hex symbols with range properties.
Changes:
Summary by cubic
Fix crashes in menuconfig and guiconfig when handling INT/HEX symbol ranges by aligning with kconfiglib’s current API. Users can now enter values without ValueError.