Include stubs for PyQt6-WebEngine too #6
Comments
toofar
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
Jun 26, 2022
My for has Webengine stubs included too. All autogenerated with no specific codemods or anything yet. Ref python-qt-tools/PyQt6-stubs#6 Switching to just PyQt6 instead of both 5 and 6 installed at the moment because ... it cases about half as many mypy errors. There are a lot of places like: if gettatt(...): # pyqt6 ... else: # pyqt5 ... that mypy has no idea about. I'm not sure the best way to guide it at this point. Even once I figure that out I'm not sure that doing one run with both 5+6 is the way to go, we might want to split mypy into two runs.
toofar
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
Jun 26, 2022
My for has Webengine stubs included too. All autogenerated with no specific codemods or anything yet. Ref python-qt-tools/PyQt6-stubs#6 Switching to just PyQt6 instead of both 5 and 6 installed at the moment because ... it cases about half as many mypy errors. There are a lot of places like: if gettatt(...): # pyqt6 ... else: # pyqt5 ... that mypy has no idea about. I'm not sure the best way to guide it at this point. Even once I figure that out I'm not sure that doing one run with both 5+6 is the way to go, we might want to split mypy into two runs.
toofar
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
Jul 3, 2022
My for has Webengine stubs included too. All autogenerated with no specific codemods or anything yet. Ref python-qt-tools/PyQt6-stubs#6 Switching to just PyQt6 instead of both 5 and 6 installed at the moment because ... it cases about half as many mypy errors. There are a lot of places like: if gettatt(...): # pyqt6 ... else: # pyqt5 ... that mypy has no idea about. I'm not sure the best way to guide it at this point. Even once I figure that out I'm not sure that doing one run with both 5+6 is the way to go, we might want to split mypy into two runs.
toofar
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
Jul 3, 2022
My for has Webengine stubs included too. All autogenerated with no specific codemods or anything yet. Ref python-qt-tools/PyQt6-stubs#6 Switching to just PyQt6 instead of both 5 and 6 installed at the moment because ... it cases about half as many mypy errors. There are a lot of places like: if gettatt(...): # pyqt6 ... else: # pyqt5 ... that mypy has no idea about. I'm not sure the best way to guide it at this point. Even once I figure that out I'm not sure that doing one run with both 5+6 is the way to go, we might want to split mypy into two runs.
toofar
added a commit
to qutebrowser/qutebrowser
that referenced
this issue
Jul 30, 2022
My fork has Webengine stubs included too. All autogenerated with no specific codemods or anything yet. Ref python-qt-tools/PyQt6-stubs#6 Switching to just PyQt6 instead of both 5 and 6 installed at the moment because ... it causes about half as many mypy errors. There are a lot of places like: if gettatt(...): # pyqt6 ... else: # pyqt5 ... that mypy has no idea about. I'm not sure the best way to guide it at this point. Even once I figure that out I'm not sure that doing one run with both 5+6 is the way to go, we might want to split mypy into two runs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like the stubs for PyQt6-WebEngine are not currently included, they are in the PyQt5-stub package.
The text was updated successfully, but these errors were encountered: