Type Hinting in PyCharm
PyCharm provides various means to assist inspecting and checking the types of the objects in your script. PyCharm supports type hinting in function annotations and type comments using the
typing module and the format defined by PEP 484.
Adding type hints
Although PyCharm supports all methods for adding types supported in PEP 484, using type hints through intention actions is the most convenient way. Depending on the interpreter you use, the type is added as an annotation (Python 3) or as a comment (Python 2).
To add a type hint, follow these steps:
Select a code element.
Select Add type hint for ....
Press Enter to complete the action or edit the type if appropriate.
Resulting Code for comments (Python 2)
Resulting Code for annotations (Python 3)
Specifying types by using comments
# type: comment to specify the types of local variables and attributes:
For comment-based type hints, PyCharm suggests an intention action that allows you to convert comment-based type hint to a variable annotation. This intention has the name Convert to variable annotation, and works as follows:
Type hints validation
Any time you're applying type hints, PyCharm checks if the type is used correctly. If there is a usage error, the corresponding warning is shown and the recommended action is suggested. Below are the validation examples.
Duplication of type declaration.
Remove either of the type declarations.
Number of arguments in the type declaration differs from the number of function arguments.
Adjust the number of the arguments.
Add the required brackets where appropriate.
Type comments with unpacking do not match the corresponding targets.
Check the target format and modify the type comment accordingly.
Incorrect syntax of
Use the suggested format and add the required brackets to wrap
PyCharm supports Python stub files with the
.pyi extension. These files allow you to specify the type hints using Python 3 syntax for both Python 2 and 3.
The stub files are created as usual, but you must specify the extension
PyCharm shows an asterisk in the left gutter for those code elements that have stubs:
Clicking the asterisk results in jumping to the corresponding stub:
With the PEP-561 support, you can install stubs as a package for a Python interpreter.
To install a stub package
Follow the procedure described in To install a package. If needed, click Manage repositories to add a repository where your stub packages reside.
Stub packages have a predefined name format, so type "-stubs" in the search field to discover them.
Complete installation by clicking Install Package.
Once added, the type hints recorded in the stub files become available in your code. For example, the following type hint for
becomes available in the following Python code
If you're using a package for which a stub analog is detected, the following message will be shown:
You can install the stub package, ignore this message and continue working with the currently installed package, or even disable the corresponding inspection in the project Settings/Preferences.
Typeshed is a set of files with type annotations for the standard Python library and various packages. Typeshed stubs provide definitions for Python classes, functions, and modules defined with type hints. PyCharm uses this information for better code completion, inspections, and other code insight features.
PyCharm is switching to Typeshed, the common repository for Python stubs. The Typeshed stubs bundled with PyCharm are shown in the project view under the node External Libraries | <Python interpreter> | Typeshed Stubs. Note that PyCharm currently uses only a few of the bundled stubs (i.e.
typing.pyi, and several others).
To override the bundled Typeshed repository with your own version, follow these steps:
Copy some or all the stubs into a directory in your project.
Mark a directory as a source root by choosing Mark Directory as | Sources Root from the context menu of the directory.
The Python skeletons repository https://github.com/JetBrains/python-skeletons is now deprecated.