Changes between Initial Version and Version 5 of Ticket #57823
- Timestamp:
- Feb 11, 2019, 1:31:21 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57823
- Property Owner set to eborisch
-
Property
Status
changed from
new
toassigned
- Property Port py-spyder py-spyder-devel removed
- Property Cc mamoll pmetzger MarcusCalhoun-Lopez reneeotten added
-
Ticket #57823 – Description
initial v5 1 Since QtPy supports PySide2 (which is now Qt's official bindings for Python) in addition to PyQt5, should it be possible for the `py-qtpy` port ( as well as any ports using it, e.g. Spyder) to allow `py-pyside2` as a substitute for `py-pyqt5`? I am not an expert on their differences, nor do I have any preference that PySide2 become MacPorts' default over PyQt5.1 Since QtPy supports PySide2 (which is now Qt's official bindings for Python) in addition to PyQt5, should it be possible for the `py-qtpy` port (~~as well as any ports using it, e.g. Spyder~~) to allow `py-pyside2` as a substitute for `py-pyqt5`? I am not an expert on their differences, nor do I have any preference that PySide2 become MacPorts' default over PyQt5. 2 2 3 If so, I imagine adding a variant `qtpy +pyside2` would be the approach for this (similar to what `py-matplotlib` has, though it doesn't use QtPy). However if the `py-qtpy` port is what ensures a Qt backend is installed, should that dependency then be removed from ports depending on qtpy (`spyder` and `spyder-devel`), or is the PyQt5 dependency used to ensure a Qt5 backend is present—i.e. when Qt4 can't be used?3 If so, I imagine adding a variant `qtpy +pyside2` would be the approach for this (similar to what `py-matplotlib` has, though it doesn't use QtPy). However if the `py-qtpy` port is what ensures a Qt backend is installed, should that dependency then be removed from ports depending on qtpy ~~(`spyder` and `spyder-devel`)~~, or is the PyQt5 dependency used to ensure a Qt5 backend is present—i.e. when Qt4 can't be used?