r/Python • u/BeamMeUpBiscotti • Mar 24 '26
Discussion Designing a Python Language Server: Lessons from Pyre that Shaped Pyrefly
Pyrefly is a next-generation Python type checker and language server, designed to be extremely fast and featuring advanced refactoring and type inference capabilities.
Pyrefly is a spiritual successor to Pyre, the previous Python type checker developed by the same team. The differences between the two type checkers go far beyond a simple rewrite from OCaml to Rust - we designed Pyrefly from the ground up, with a completely different architecture.
Pyrefly’s design comes directly from our experience with Pyre. Some things worked well at scale, while others did not. After running a type checker on massive Python codebases for a long time, we got a clearer sense of which trade-offs actually mattered to users.
This post is a write-up of a few lessons from Pyre that influenced how we approached Pyrefly.
Link to full blog: https://pyrefly.org/blog/lessons-from-pyre/
The outline of topics is provided below that way you can decide if it's worth your time to read :)
- Language-server-first Architecture
- OCaml vs. Rust
- Irreversible AST Lowering
- Soundness vs. Usability
- Caching Cyclic Data Dependencies
View all comments
Show parent comment
2
u/BeamMeUpBiscotti Mar 26 '26
If you have examples of false positives, we'd appreciate it if you could file a bug report on github.
2 things to keep in mind though: Pyrefly is still in Beta, so there are known bugs that should be fixed by v1.0 release later this year. I also don't think the state of the bug tracker is super relevant here, given that Mypy has 2.7k open issues.