Skip to content
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

Use PySide6 instead of PySide2 in CI testing #1685

Merged
merged 3 commits into from
Aug 9, 2022
Merged

Conversation

mdickinson
Copy link
Member

@mdickinson mdickinson commented Aug 8, 2022

This PR changes the .[test] requirements to use PySide6 instead of PySide2, and removes the version constraint on the PySide install.


EDIT: Updated to use PySide2 for Python 3.6 and 3.7, and PySide6 for Python >= 3.8. Currently, the PyPI eggs for PySide6 claim only to work for Python < 3.11, so we add that restriction as well.

While we're here, we also clean up an outdated Sphinx version restriction.

@mdickinson mdickinson changed the title Attempt to use PySide6 in test suite Use PySide6 instead of PySide2 in CI testing Aug 8, 2022
@mdickinson mdickinson merged commit e0c6008 into main Aug 9, 2022
@mdickinson mdickinson deleted the ci-use-pyside6 branch August 9, 2022 07:46
mdickinson added a commit that referenced this pull request Aug 9, 2022
This PR changes the .[test] setup.py requirements to use PySide6 instead of PySide2 for Python3.8 and later, and removes the version constraint on the PySide install. We exclude Python 3.11, since the PySide6 eggs available on PyPI claim not to work on 3.11.

While we're here, we also clean up an outdated Sphinx version restriction.

(cherry picked from commit e0c6008)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants