Details
-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
The python stubs files (pyi files) contain type-hinting information of normal Python modules. They are annotations that specify the data types of function arguments and return types.
When generating the first .pyi files, the existence of the MyPy module was mostly ignored. We tried to follow the specification in PEP-484 and modelled the annotations close to the specification.
Meanwhile, the specification was much extended and contains also constants, variables etc., and quite a number of other related PEPs has evolved. PyPy and other tools were improved, substantially.
We want to fully support MyPy with all extended features and correctness as good as possible. This activity will need a number of check-ins until that goal is reached.
Attachments
Issue Links
- depends on
-
PYSIDE-1520 Type Checking using mypy errors erroneously
- Closed
-
PYSIDE-1638 Incomplete autocomplete support via .pyi files
- Closed
-
PYSIDE-1713 SignalInstance emit signatures incorrect
- Closed
-
PYSIDE-1731 Reg->6.2.2/MyPy: Type of Qt.AlignmentFlag incompatible with Qt.Alignment
- Closed
-
PYSIDE-1603 Missing signals in stubs
- Closed
-
PYSIDE-1318 Wrong or incomplete type stubs for signals/slots
- Closed
- relates to
-
PYSIDE-1955 mypy error: "QObject" has no attribute "tr"
- Closed
-
PYSIDE-2235 typing: QtWidget.setParent can be optionally None
- Closed
- mentioned in
-
Page Loading...