You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for clarifying the release scope. I can split this into two PRs: an Arrow-backed string fix suitable for backporting to 3.1.x, and a separate categorical fix.
The Arrow PR would exclude the empty-string dummy column and preserve the row count when no labels remain, without changing categorical behavior.
Would that split work for you? I would use Refs #71887 for the Arrow PR so that the issue remains open for the categorical part.
Activity
AntsiferovBogdan commentedon Nov 4, 2026
/take
[-]BBUG: Series.str.get_dummies adds "NaN" / "" column for categorical / Arrow-backed strings[/-][+]BUG: Series.str.get_dummies adds "NaN" / "" column for categorical / Arrow-backed strings[/+]jorisvandenbossche commentedon Nov 4, 2026
This is a regression from 2.x for strings (due to implicit object -> str dtype change), so marking for 3.1.x
jorisvandenbossche commentedon Nov 4, 2026
Although for
categoryit is long standing behaviour, so there we should maybe not fix it in a patch releaseAntsiferovBogdan commentedon Nov 4, 2026
Thanks for clarifying the release scope. I can split this into two PRs: an Arrow-backed string fix suitable for backporting to 3.1.x, and a separate categorical fix.
The Arrow PR would exclude the empty-string dummy column and preserve the row count when no labels remain, without changing categorical behavior.
Would that split work for you? I would use Refs #71887 for the Arrow PR so that the issue remains open for the categorical part.