2025 Python Type System and Tooling Survey is out!

The 2025 Python Type System and Tooling Survey is out!

Take the survey here: Python Type System and Tooling Survey 2025

I also want to say a huge thank-you to the folks who commented on our earlier post with feedback on the draft survey!

Stay tuned for another post with the survey results in a few weeks!

This survey was developed with support from the Pyrefly team at Meta, the PyCharm team at JetBrains, and the typing community on discourse.python.org

10 Likes

Could you write about who is creating / managing the survey, whether this is an official survey from the PSF / cpython / Typing Council, etc?

After clicking through to the survey, it has a much clearer intro that would be appropriate to edit into your post.

1 Like

It is mentioned pretty clearly in the first section on the survey itself, but yes I can update the post too

Emacs (with a language server protocol)

Nit: Perhaps you meant to say “with a language server”? There’s only one Language Server Protocol, but multiple language servers and language clients.

While filling this out, I realized that it’s really hard to answer the question about what typing needs the most in terms of new features. I didn’t realize this while looking over the proposed questions, but filling it in, I found I was choosing pretty much at random from a bunch of orthogonal missing capabilities.

With the benefit of hindsight, I wish I had been asked to rank several well known ideas, and separately for a key feature not listed. Of course, I say that imagining that the list would contain exactly the features I consider important, so take this meta-feedback with a grain of salt.

7 Likes

Thanks all who filled out the survey! We have now closed the survey for responses and are working on reviewing the data, so keep a look out for another post on that in the near future. In the meantime we’d like to share some preliminary results, overall looking pretty similar to last year:

7 Likes