Repository navigation
fix: preserve original skeleton in KeyError when fuzzy format_skeleton finds no match - #1275
Merged
Merged
Conversation
akx
approved these changes
Oct 30, 2026
…n finds no match Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
akx
force-pushed
the
fix/format-skeleton-keyerror-none
branch
from
October 30, 2026 11:20
98e415b to
6dbe0f0
Compare
akx
enabled auto-merge (squash)
October 30, 2026 11:21
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1275 +/- ##
=======================================
Coverage 93.56% 93.56%
=======================================
Files 27 27
Lines 4939 4939
=======================================
Hits 4621 4621
Misses 318 318
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
When
format_skeletonis called withfuzzy=Trueandmatch_skeletonfinds no close match, it returnsNone. The subsequentlocale.datetime_skeletons[skeleton]lookup then raisesKeyError: None, which is confusing since it hides the skeleton that was actually requested.This change falls back to the original skeleton when
match_skeletonreturnsNone, so the error isKeyError: 'G'instead ofKeyError: None, consistent with thefuzzy=Falsebehavior.