Fix pandas 3.0 KeyError in Enum.encode() for Series with non-integer index #428
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.
Summary
Fixes #427
In pandas 3.0, string columns use
StringDtypeby default. When a pandas Series has a non-integer index (e.g., string index),array[0]does label-based lookup (looking for key"0") instead of positional access, causingKeyError: 0.This broke policyengine-us when enabling pandas 3.0 support - specifically the
countyvariable tests failed with:Changes
Enum.encode()to use.iloc[0]for pandas Series to ensure positional accesstest_enum_encode_pandas_series_with_enum_items- basic Series with default indextest_enum_encode_pandas_series_with_string_index- Series with string index (the failing case)Test plan
Related
🤖 Generated with Claude Code