Python Typing Survey 2026: AI Tools and the Shifting Checker Landscape

The 2026 Python Typing Survey (1,794 responses, mostly experienced developers—76.4% had used Python five or more years) found that type hint use changed little over three years while checker selection shifted sharply. Among respondents who named their checkers, half used more than one. Missing library type information remained the most common difficulty.

Key findings

• Type hint use changed little across three years, but checker selection changed sharply; among respondents who reported which checkers they use, half selected more than one.
• Missing type information in third-party libraries was the leading difficulty, selected by 65.1% of 1,486 respondents; 44.6% said the type system could not describe everything their code does.
• Respondents repeatedly named Django, SQLAlchemy, Pydantic, NumPy, pandas, and Polars as problem areas; among 156 free-text answers, 22 described dynamic constructs, decorators, metaprogramming, or framework behavior, ten described arrays, dataframes, or scientific typing, and at least eight described inaccurate, incomplete, or too-broad annotations.
• AI tools wrote type hints for 42.5% of 1,517 respondents, and 32.6% wrote types to improve AI-generated code; 61.0% reported using at least one of the four listed AI-in-typing activities.
• When asked how useful types are for better AI-assisted coding, 29.8% of 1,551 respondents chose “I’m not sure”—nearly four times the 7.7% uncertainty rate for runtime guarantees, the next-highest of six benefits.
• Frequency of use changed which problems stood out: 41.6% of rare/occasional users found the type system too complex or verbose versus 14.5% of frequent users; missing library typing affected 36.2% of the lower-frequency group and 70.0% of the higher-frequency group.
• Complexity was reported by 18.2% of respondents with zero to two years of typing experience, 16.0% with three to six years, and 21.0% with seven or more.

Limitations

• The findings on AI leave an open question about which interactions between AI tools and type checkers actually help developers; empirical evidence is still needed.

Practical implications

• Typing documentation can assume Python experience and should show how to add types to an existing repository.
• Projects using multiple checkers would benefit from clear explanations of intentional differences between them.
• Better Callable syntax remains a practical area for standards work, provided improvements keep common typing tasks straightforward.

Key findings

• AI tools wrote type hints for 42.5% of 1,517 respondents; 24.4% of 1,517 had an AI coding tool invoke their checker.

Blogs · Meta Engineering · Publisher website: engineering.fb.com · Last verified 31 October 2026 · Catalog ID 127995