chore: Remove pyside2 form extras during constraints generation#1411
Conversation
The `pyside2`no longer have releases and is about to remove from project (as napari 0.7.0 changed bundle to `PySide6`)
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR updates the dependency constraints generation workflow to stop including the deprecated File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
📝 WalkthroughWalkthroughThis PR updates the Python dependency constraint compilation workflow step, replacing the ChangesDependency Compilation Extras
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/upgrade-dependencies.yml (1)
36-36: Adjust scope:pysidealias doesn’t affect the workflow’s constraint generationThe workflow generates constraints with
--extra pyside6(not--extra pyside), and there’s no usage ofPartSeg[pyside]/--extra pysideelsewhere in the repo. Sopyproject.toml’spyside = ["PartSeg[pyside2]"]is not an active contract mismatch with the current constraints-generation step.Optional: if you intend the generic
pysideextra to mean “current” backend (PySide6), consider renaming/updating that alias; otherwise leave it for the PySide2 legacy backend.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/upgrade-dependencies.yml at line 36, The workflow uses flags=(--extra pyqt6 --extra pyside6 --extra test --extra pyinstaller_base) while pyproject.toml defines pyside = ["PartSeg[pyside2]"], so the workflow’s constraint generation targets pyside6 not the pyside alias; fix by making the intent explicit: either add/replace --extra pyside in the flags tuple to match the pyproject alias (flags (…) include --extra pyside) or update the pyproject.toml alias pyside to reference the current backend (e.g., Point to PartSeg[pyside6] or rename the alias to pyside2 if you intend the legacy backend); update the symbol names flags, --extra pyside6, and the pyproject.toml entry pyside = ["PartSeg[pyside2]"] accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/upgrade-dependencies.yml:
- Line 36: The workflow uses flags=(--extra pyqt6 --extra pyside6 --extra test
--extra pyinstaller_base) while pyproject.toml defines pyside =
["PartSeg[pyside2]"], so the workflow’s constraint generation targets pyside6
not the pyside alias; fix by making the intent explicit: either add/replace
--extra pyside in the flags tuple to match the pyproject alias (flags (…)
include --extra pyside) or update the pyproject.toml alias pyside to reference
the current backend (e.g., Point to PartSeg[pyside6] or rename the alias to
pyside2 if you intend the legacy backend); update the symbol names flags,
--extra pyside6, and the pyproject.toml entry pyside = ["PartSeg[pyside2]"]
accordingly.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 51c3f531-3f40-4b24-9173-20e82009e464
📒 Files selected for processing (1)
.github/workflows/upgrade-dependencies.yml



The
pyside2no longer have releases and is about to remove from project (as napari 0.7.0 changed bundle toPySide6)Summary by Sourcery
CI:
Summary by CodeRabbit