-
Notifications
You must be signed in to change notification settings - Fork 20
Pin PySide to 6.10 for now #369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -66,7 +66,7 @@ jobs: | |||||
| - name: Install Python dependencies | ||||||
| run: | | ||||||
| python -m pip install --upgrade pip | ||||||
| pip install pyfakefs PySide6 vermin requests || true | ||||||
| pip install pyfakefs "PySide6<6.11" vermin requests || true | ||||||
|
||||||
| pip install pyfakefs "PySide6<6.11" vermin requests || true | |
| pip install pyfakefs "PySide6<6.11" vermin requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR title/description says to pin PySide to 6.10, but the constraint
PySide6<6.11is only an upper bound and could allow older majors/minors if 6.10 wheels aren’t available for a given Python version. If the intent is specifically 6.10.x, consider using a tighter specifier (e.g.,PySide6>=6.10,<6.11orPySide6~=6.10.0) so the workflow can’t silently downgrade.