[MacPorts] #57823: py-qtpy: allow py-pyside2 instead of py-pyqt5

MacPorts noreply at macports.org
Mon Feb 11 01:31:21 UTC 2019


#57823: py-qtpy: allow py-pyside2 instead of py-pyqt5
------------------------------------------+----------------------
  Reporter:  chrstphrchvz                 |      Owner:  eborisch
      Type:  enhancement                  |     Status:  assigned
  Priority:  Normal                       |  Milestone:
 Component:  ports                        |    Version:
Resolution:                               |   Keywords:
      Port:  py-qtpy py-pyqt5 py-pyside2  |
------------------------------------------+----------------------
Changes (by chrstphrchvz):

 * port:  py-qtpy py-pyqt5 py-pyside2 py-spyder py-spyder-devel => py-qtpy
     py-pyqt5 py-pyside2


Old description:

> 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.
>
> 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?

New description:

 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.

 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?

--

Comment:

 Never mind about having Spyder ports use PySide2; upstream has decided to
 not support it for the time being: https://github.com/spyder-
 ide/spyder/issues/6894.

 If nothing using QtPy currently "needs"/"really should have" PySide2 as an
 alternative to PyQt5, then I don't mind this being closed or put off
 indefinitely/wishlisted. I intended this more as a suggestion in case it
 were trivial to add, but it sounds like that's definitely not the case.

-- 
Ticket URL: <https://trac.macports.org/ticket/57823#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list