Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:2
-
Sprint:TSSW Sprint - Jan 30 - Feb 13
-
Team:Telescope and Site
-
Urgent?:No
Description
Please help to install the PySide6 in LSST develop image in additional to PySide2. Right now, the M2 Python EUI and M1M3 EUI are using the PySide2 as the QT library. We would like to upgrade the EUIs to PySide6.
However, we may want to make sure the pytest-qt and other packages (xorg-x11-server-Xvfb and pytest-xvfb support unit test on Jenkins) or platforms (AlmaOS and MacOS) can still work after the upgrade of EUI packages.
Therefore, the PySide2 and PySide6 might need to coexist for some time before the upgrade and test are done. Thanks!
Attachments
Issue Links
Activity
| Labels | M1M3 M2 |
| Description |
Please help to install the *PySide6* in LSST develop image in additional to *PySide2*. Right now, the M2 Python EUI and M1M3 EUI are using the *PySide2* as the QT library. We would like to upgrade the EUIs to *PySide6*.
However, we may want to make sure the *pytest-qt* and other packages (support unit test on Jenkins) or platforms (AlmaOS and MacOS) can still work after the upgrade of EUI packages. Therefore, the *PySide2* and *PySide6* might need to coexist for some time before the upgrade and test are done. Thanks! |
Please help to install the *PySide6* in LSST develop image in additional to *PySide2*. Right now, the M2 Python EUI and M1M3 EUI are using the *PySide2* as the QT library. We would like to upgrade the EUIs to *PySide6*.
However, we may want to make sure the *pytest-qt* and other packages (*xorg-x11-server-Xvfb* and *pytest-xvfb* support unit test on Jenkins) or platforms (AlmaOS and MacOS) can still work after the upgrade of EUI packages. Therefore, the *PySide2* and *PySide6* might need to coexist for some time before the upgrade and test are done. Thanks! |
| Sprint | TSSW Sprint - Jan 16 - Jan 30 [ 1212 ] | |
| Labels | M1M3 M2 | M1M3 M2 ts_cycle_build |
| Story Points | 1 |
| Story Points | 1 | 0 |
This will be part of the cycle 29 build.
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
After talking to Te-Wei, I also will upgrade the version of PySide2 from 5.13.2 to 5.15.8.
Both the newer PySide2 conda package and the PySide6 conda package require newer versions of the pyqt and pyqt-impl conda packages. Neither are available on conda-forge so we will need to build them ourselves. I will work on this next sprint.
| Sprint | TSSW Sprint - Jan 16 - Jan 30 [ 1212 ] | TSSW Sprint - Jan 30 - Feb 13 [ 1216 ] |
| Story Points | 0 | 1 |
| Story Points | 1 | 2 |
It turns out that ts-develop pinned the version of pyqt which prevented PySide2 from updating to a newer version. This has been fixed by removing the pyqt dependency from ts-develop and by moving all PySide2 dependencies from the base-sqre Dockerfile to ts-develop. Petr helped me locate the correct conda packages for PySide2 and PySide6. Now the installation works fine. I am building an docker.io/lsstts/develop-env:PYSIDE Docker image for Te-Wei and Petr to test.
I prepared the ts-dockerhub.lsst.org/develop-env:PYSIDE docker image containing both PySide2 and PySide6 and asked Petr Kubanek and Te-Wei Tsai to test it.
Please try out the develop-env docker image I created and mark this ticket as Reviewed when you're happy with it.
| Reviewers | Petr Kubanek, Te-Wei Tsai [ pkubanek, ttsai ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
Looks good to me. I would test the docker image at DM-37454. It might happen in the next week. If there was the problem, we could reopen this ticket. Thanks!
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Thanks Te-Wei. I'd prefer a new ticket in case of a problem but we can discuss that if any is found.
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
I created a docker.io image as well, since Te-Wei doesn't have a ts-dockerhub account. The image can be found on docker.io/wvreeven/develop-env.
+1 on this. Shall be as trivial as adding mamba install -y pyside6. pyside2 and pyside6 coexistence shall not be an issue, as they live in pyside2/pyside6 namespace.