New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch back to upstream PyQt5-stubs for mypy #5368
Comments
Ah, right, I'll probably need to resolve python-qt-tools/PyQt5-stubs#15 first. |
The PR for that issue: python-qt-tools/PyQt5-stubs#36 has been merged. Do you think it's possible to switch QB to use the latest package now? |
Those stubs aren't in the master branch yet: python-qt-tools/PyQt5-stubs#42 Even then, there's still a lot to be fixed in the stubs (and perhaps in qutebrowser's codebase) - right now, I see:
and with the new modules in, that number might raise. |
The new files are in
I'll see if I can take a look at those. |
Almost there after some changes:
Todo:
|
We accidentally passed a list of HintLabels instead of a list of elements there. That worked by accident, because all we use with number hints is actually the length of that list. See #5368
Right now, qutebrowser is still running with its own outdated fork of PyQt5-stubs. We should switch back to the upstream project.
From a quick test, that results in 456 new mypy errors (some of them I don't quite understand), so that will likely need a bit more work first.
The text was updated successfully, but these errors were encountered: