Summary: | dev-python/spyder-6.0.1 fails to start with error: "ImportError: cannot import name 'QTextCodec' from 'qtpy.QtCore'", when using pyside{2,6} as the QtPy backend. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Tulupov <vaxxabait> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | nowa, vaxxabait |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/spyder-ide/spyder/issues/20201 https://github.com/spyder-ide/qtpy/issues/233 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Error log
Error log when PySide6 is used, without unittest plugin |
Description
Michael Tulupov
2024-09-24 19:26:49 UTC
Created attachment 903665 [details]
Error log
Pyside support in Spyder is in an experimental stage, still qt6 should work via pyqt6.
> but either of [pyside6 pyqt5 pyqt6 pyside2] is not specified as mandatory useflag.
The either off requirement is part of the QtPy ebuild and does not need to be specified here.
The failure seems to originate specifically in the spyder-unittest plugin, please try again without this plugin installed and please also try with pyqt6 instead of pyside6. Disabling multiple backends in qtpy is not an option, it defeats the entire purpose of that package and will create a dependency mess with other packages depending on it. (In reply to Andrew Nowa Ammerlaan from comment #4) > Disabling multiple backends in qtpy is not an option, it defeats the entire > purpose of that package and will create a dependency mess with other > packages depending on it. OK, got it, my initial impression was that backend choice is baked during build time, but i found QT_API variable. (In reply to Andrew Nowa Ammerlaan from comment #2) > Pyside support in Spyder is in an experimental stage, still qt6 should work > via pyqt6. OK, clear. Do you think it is a good idea to mention in spyder's pkg_postinst that Pyside support is experimental and PyQt5 or 6 are recommended and can be forced by QT_API ? Created attachment 903666 [details] Error log when PySide6 is used, without unittest plugin (In reply to Andrew Nowa Ammerlaan from comment #3) > The failure seems to originate specifically in the spyder-unittest plugin, > please try again without this plugin installed and please also try with > pyqt6 instead of pyside6. with unittest removed and PySide6 - still does not work. Seems like a problem somewhere near legacy plugin support (from Spyder 5.x). new log is in attachment. PyQt6 will try later....maybe (wants too many new packages). For now I will stay with PyQt5, which works fine for me. Still if new suggestions/patches will come for PySide6 - I'm in to try. Thanks for quick support ! (In reply to Michael Tulupov from comment #6) > (In reply to Andrew Nowa Ammerlaan from comment #2) > > Pyside support in Spyder is in an experimental stage, still qt6 should work > > via pyqt6. > > OK, clear. Do you think it is a good idea to mention in spyder's > pkg_postinst that Pyside support is experimental and PyQt5 or 6 are > recommended and can be forced by QT_API ? I don't think this is required since QtPy already prefers PyQt* over PySide* if both are installed, and both the PyQt5 and PyQt6 flags on QtPy are enabled by default. Which means that the default configuration should work out of the box for both Qt5 and Qt6. |