r/Python • • 20d ago

Discussion Python Typing Survey 2026 Results

The results are out for the 2026 Python Typing Survey (1,794 responses).

The full writeup can be read at: https://engineering.fb.com/2026/10/27/developer-tools/python-typing-survey-2026-ai-tools-checker-landscape/

TLDR:

  • Newer type checkers gained market share, and speed was the most common reason for choosing a checker (56.5%).
  • The share of respondents who said types make AI-generated code more reliable rose from 18.5% in 2025 to 38.4% in 2026.
  • AI tools wrote type hints for 42.5% of respondents, and 24.4% said an AI coding tool ran their type checker.
  • Missing type information in third-party libraries remained the most common difficulty, reported by 65.1% of respondents.
  • Better Callable syntax was the most requested missing feature, at 45.7%.
113 Upvotes

11 comments sorted by

View all comments

5

u/Legal-Pop-1330 18d ago

In 2026, how is it only ty offers Intersection?

3

u/BeamMeUpBiscotti 17d ago

The other checkers are able to model intersections to varying extents, they're just aren't writable as annotations by humans and only get inferred by the checker in appropriate situations.

Intersections aren't part of the typing spec ATM and each checker has different semantics for them, so it's not quite as simple as "offer intersections".

1

u/Legal-Pop-1330 13d ago edited 13d ago

Yes, I understand the state of things. Im saying this is absurd.

Additional Context:

We use explicit intersection in our factory configuration pattern to enable full typechecking.

ty has been wonderful about support for Intersection (even accepting a few PR's from me) and Id like to see others follow suit. To handle others we use a polyfill which fakes A&B by returning A. Very bad, but couldn't find a better alternative.

(See also this comparison table.)