PyCharm 2026.3 ships 303 fixes, from functools.partial signatures to Ruff fixes on save
JetBrains has published a list of the smaller changes in PyCharm 2026.3, separate from the headline features of the release such as JetBrains Air, workspaces, support for Python 3.15 lazy imports and a redesigned interpreter widget. According to the post by Will Vincent and Morgan Bartholomew, the release carries 303 fixes and improvements to everyday Python work, some of them for issues first reported more than ten years ago.
The largest group concerns type inference. PyCharm now works out the remaining parameters of a functools.partial object, checks their types and accepts the object where a Callable is expected, which closes four long-standing tickets (PY-35363, PY-33618, PY-25698, PY-36385). Calling a method on a bounded type variable now keeps its return type instead of falling back to Any, and nested lists, optional values, dictionary literals and tuple unpacking produce fewer false warnings. The post also lists support for PEP 747's TypeForm[T].
Suppression gets finer controls. Short codes are accepted in # type: ignore[...], a new # pycharm: ignore[...] comment silences a single PyCharm inspection, and unknown suppression codes are flagged so that a typo does not hide nothing.
For tests, the IDE now completes the mocker fixture from pytest-mock, navigates to mocker.patch() targets and offers the methods of a class passed to Mock(spec=...) or Mock(spec_set=...). Invalid unittest.mock.patch() targets are flagged, and a custom unittest runner script such as Django's tests/runtests.py can feed results into the test tree if it uses unittest.TextTestRunner.
External tools are broader too. Zuban, a mypy-compatible checker and language server, joins ty, Pyrefly and basedpyright. With Ruff, Optimize Imports now removes unused imports as well as sorting them, fixes can run on save or before a commit, and an Apply Ruff Fixes action works across a selected scope up to the whole project.
Framework support picks up Django 6.0 task run configurations, URL-name completion for Django REST framework's reverse(), fewer false warnings for FastAPI path parameters supplied through dependencies, and better completion for SQLAlchemy declarative models.

Why it matters
Most of these items remove false positives rather than add features. An inspection that is wrong about partial or about a bounded type variable teaches people to ignore warnings, so the new per-inspection suppression and the check for unknown codes are as useful as the inference fixes themselves.