Making webengine optional on conda-forge

[hmaarrfk]

Comment:

QtWebengine on conda-forge has been seriously lagging. For example, we haven't been able to get the courage to build the latest version of 5.15 since nobody has had the time for build Windows or OSX in a reliable timeline.

I'm wondering if those at conda-forge would be willing to backport:

• https://github.com/spyder-ide/spyder/pull/22198
• https://github.com/spyder-ide/spyder/pull/22199

And move

    - pyqtwebengine >=5.10,<5.16

to a run constraint.

The most visible feature users would loose is the help menu. I am unsure how to resolve this with the current resources at conda-forge's disposal given the amount of time it takes for qt-webengine to finish compiling.

[hmaarrfk]

And to make things easier, here are the patches I used in my own work to get spyder working wtihout webengine.

I haven't done much testing, I can just confirm that it "opens"

no_qt_webengine_patch.zip

[ccordoba12]

And move

• pyqtwebengine >=5.10,<5.16

to a run constraint.

How does that work? The latest qt/pyqt 5 versions will be pulled but if not matching pyqtwebengine is found, it'll be skipped?