-
Notifications
You must be signed in to change notification settings - Fork 7
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
MNT/BLD: unpin pyqt #74
Conversation
These tests are failing due to the bluesky update I think |
Should we constrain bluesky or update based on the thoughts in #73 ? |
I want to remember hearing something about bluesky 1.11 being pulled/reverted, or at least thought about more. That tips my scales toward pinning, on the off chance some implementation details change. It's also less work for us now, at the cost of being confused about who made the pins later 😆 |
@@ -0,0 +1,22 @@ | |||
74 free-pyqt |
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.
free pyqt 🙌
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 bluesky pin is also appropriate, we can unpin it when we make the preprocessors here compatible with plans that use the new message introduced in 1.11
Description
Unpin pyqt, leaving it at 5.x.
Motivation and Context
We're looking forward to Python 3.11 everywhere.
hutch-python > nabs
dependency means that hutch-python and these libraries currently requirepyqt < 5.15
in our environment. Those versions are not available for Python 3.11. PyDM and our other libraries are now (likely/mostly) compatible with PyQt 5.15, so releasing the pin here is our next step toward that transition.How Has This Been Tested?
Untested. Relying on CI, which is likely to fail due to bluesky-related changes.
Where Has This Been Documented?
This PR text.
Pre-merge checklist