docs(v1): cover unlabeled-operand and grouper cases; fold MI-level projection#855
Merged
Merged
Conversation
…to MI row The migration guide's fix table covered the core absence + alignment + aux-coord + MultiIndex-dim + groupby-result cases, but three issue-backed v1 changes were under-covered. Add rows and mirror two into the release-notes v1 summary: - Unlabeled operand (numpy / list / polars) pairs to dims by size; ambiguous or no-size-match raises (#736) — the object-scope premise. - A reordered/mismatched groupby grouper raises rather than reindexing positionally (#827). - MultiIndex-level projection: v1 rejects the MultiIndex *dimension* at construction, so the per-level-input case is folded into the existing MultiIndex row — decompose with reset_index, then project by the level aux coord. (The convention.md §11 example still shows the legacy-shaped `.get_level_values` snippet, which cannot run under v1 — flagged for the spec pass.) Release notes already carry the level-projection deprecation separately, so only #736 and the grouper point are mirrored there. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
FBumann
force-pushed
the
docs/v1-migration-coverage
branch
from
July 20, 2026 08:59
87c04f2 to
13dede3
Compare
FBumann
changed the title
This was referenced Jul 20, 2026
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
1 participant
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.
Closes a coverage gap in the v1 migration guide, part of the #717 "polish the migration guide / release notes" checklist items.
Note
The following was generated by AI.
I cross-checked every issue-backed v1 behavior change (spec §1–§13 + object scope) against the guide's fix table. The core cases were covered; a few were under-covered.
groupbygrouper raises rather than reindexing positionallysnapshot(PyPSA multi-investment)MultiIndex-level projection — verified, then merged. I initially added a standalone row whose fix used
expr.indexes["snapshot"].get_level_values("period")(fromconvention.md§11). Testing on the branch showed that snippet cannot run under v1: v1 rejects apd.MultiIndexdimension at construction (add_variablesraisesValueError: ... does not support ... reset_index('snapshot')), so.indexes["snapshot"]is never a MultiIndex. The correct v1 flow is decompose-then-project-by-aux-coord, which is a consequence of the MultiIndex-dim rejection — so it's folded into that row rather than duplicated.Note
Follow-up for the spec pass:
convention.md§11's own example carries the same legacy-shaped.get_level_valuessnippet and should be corrected to the flat-dim / aux-coord idiom.Files
doc/migrating-to-v1.rst— unlabeled-operand row, grouper row, MultiIndex row extended to cover per-level inputsdoc/release_notes.rst— two new bullets in the v1 summary (v1 convention: pair unlabeled operands with dimensions by size, raise on ambiguity #736, groupby fast path matches Series/DataArray groupers by position, not by label #827)