Records/pypi/polars-runtime-32/1.43.2/DataFrame.group_by

shared with 2 packages — this evidence cannot say whose API it is

Published samples

• polars-runtime-32 1.43.2: Port pandas DataFrame code to polars on Alpine, without the wheel surprise or the silently wrong answers Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. MIGRATIONpolars.DataFramepolars.LazyFramepolars.colpolars.lenDataFrame.filterDataFrame.selectDataFrame.with_columnsDataFrame.with_row_indexDataFrame.group_byGroupBy.aggLazyFrame.collectLazyFrame.explainLazyFrame.collect_schemaExpr.map_elementsExpr.aliasSeries.is_nullSeries.is_nanSeries.fill_nullSeries.fill_nanSeries.eq_missingpolars.exceptions.ColumnNotFoundErrorpolars.exceptions.DuplicateErrorpolars.exceptions.PerformanceWarningDataFrame.vstackDataFrame.hstackDataFrame.extendDataFrame.insert_columnDataFrame.drop_in_placepython 3.12 MIT-0 · 2026-08-14

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-09-15

Failure clusters

• observed PROJECT_PROCESS Evidence gap ×4 1.43.2 os=windows · runtime=python@3.10
  Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-14 · Last seen: 2026-08-17
  Diagnostic re-verification candidate
  Where does this failure start and stop?