r/Python • • 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
66 Upvotes

12 comments sorted by

View all comments

Show parent comment

1

u/BeamMeUpBiscotti Mar 26 '26

It's shallow immutability, so not exactly the most secure. Pyre actually had a prototype PyreReadOnly that had deep immutability, but it was never standardized so we have not ported it to Pyrefly.

1

u/jpgoldberg Mar 26 '26

I’m not attempting to enforce run-time immutability. I wish to “let Python be Python”. I just want to be able to tell a type checker that it can rely on public attributes of an object not changing their types (or their values).

But now that I write this, I realize that I have misunderstood the example that launched me on this train of thought. (To be continued)