Repository navigation
fix(leaderboard): pin pyfixest<0.70 - #356
Merged
houtanb merged 1 commit intoNov 9, 2026
Merged
Conversation
pyfixest 0.70.0 (released 2026-11-08) rejects a fixed-effect column of object dtype, and
`two_way_fixed_effects` passes `question_pk` and `model_pk` as plain object columns:
FixedEffectEvaluationError: Fixed-effect column `model_pk` has unsupported object dtype.
The requirement had no upper bound, so every fresh install, CI and the next leaderboard deploy
alike, picks up 0.70.0 and the fit fails. Cap it at the last version the code was run with; casting
the key columns to `string` and lifting the cap is a separate change.
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.
pyfixest 0.70.0 (released 2026-11-08) rejects a fixed-effect column of object dtype, and
two_way_fixed_effectspassesquestion_pkandmodel_pkas plain object columns:The requirement had no upper bound, so every fresh install, CI and the next leaderboard deploy alike, picks up 0.70.0 and the fit fails. Cap it at the last version the code was run with; casting the key columns to
stringand lifting the cap is a separate change.