# Your Python. Your Voice. Join the Python Developers Survey 2026!

**URL:** <https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883>\
**Category:** PSF\
**Created:** [January 26, 2026, 1:33pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883 "2026-01-26T13:33:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![riecatnor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/riecatnor/32/15602_2.png) [@riecatnor](https://discuss.python.org/u/riecatnor)\
**Post date:** [January 26, 2026, 1:33pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/1 "2026-01-26T13:33:06Z")

</div>

Hi folks 👋

I am posting today to share that the 2026 Python Developers Survey is now open! The PSF partners with JetBrains to run this survey to capture the current state of the Python language and its surrounding ecosystem. I think the question of timing will come up, so I want to share that we intentionally launched the survey in January (later than years prior) so that data collection and results can be completed and shared within the same calendar year.

We encourage you to contribute to our community’s knowledge by sharing your experience and perspective. Your participation is valued! The survey should only take you about 10-15 minutes to complete.

### [\>\>\> Contribute to the Python Developers Survey 2026 \<\<\<](https://surveys.jetbrains.com/s3/python-developers-survey-2026)

We aim to reach even more of our community and ensure accurate global representation by highlighting our localization efforts:

- The survey is translated into Spanish, Portuguese, Chinese, Korean, Japanese, German, French, and Russian.
- To assist individuals in promoting the survey and encouraging their local communities and professional networks we have created a [Promotion Kit](https://docs.google.com/document/d/1C3r-dFY5LmklzCnf72vfeehzRqCCDuXzK8xKuwBES1Y/edit?usp=sharing) with images and social media posts translated into a variety of languages. We hope this promotion kit empowers folks to spread the invitation to respond to the survey within their local communities.
  - We’d love it if you’d share one or more of the posts below to your social media or any community accounts you manage, as well as share the information in discords, mailing lists, or chats you participate in.
  - If you would like to help out with translations you see are missing, please request edit access to the doc and share what language you will be translating to. Translation into languages the survey may not be translated to is also welcome!

- If you have ideas about what else we can do to get the word out and encourage a diversity of responses, please comment on this thread.

We hope that highlighting these localization efforts boosts our efforts to capture a representation of how Python is used across the ENTIRE globe!

p.s. There is also a chance to win a prize 🎁😁

---

<div class="post-metadata">

**Author:** ![JakobStadler](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jakobstadler/32/18754_2.png) [@JakobStadler](https://discuss.python.org/u/JakobStadler)\
**Post date:** [January 26, 2026, 10:03pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/2 "2026-01-26T22:03:39Z")

</div>

Any reason why pymanager isn’t an option for “What do you typically use to upgrade your Python version?”

Since it’s a first party tool, I would assume that adoption numbers are of interest.

---

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [January 26, 2026, 10:51pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/3 "2026-01-26T22:51:11Z")

</div>

> [@JakobStadler](#):
>
> Any reason why pymanager isn’t an option

I assumed it was covered under “[python.org](http://python.org)”.

---

<div class="post-metadata">

**Author:** ![srittau](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/srittau/32/237_2.png) [@srittau](https://discuss.python.org/u/srittau)\
**Post date:** [January 27, 2026, 8:40am UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/4 "2026-01-27T08:40:38Z")

</div>

There is a mandatory question about hobbies. While I find it questionable that this is asked at all in a developer’s survey, it’s honestly out of line that this question is mandatory. (“I have no hobbies” is not an appropriate option for “I don’t want to answer this question.”) Could this please be changed?

---

<div class="post-metadata">

**Author:** ![riecatnor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/riecatnor/32/15602_2.png) [@riecatnor](https://discuss.python.org/u/riecatnor)\
**Post date:** [January 27, 2026, 12:42pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/5 "2026-01-27T12:42:01Z")

</div>

Thanks for the feedback so far, and keep it coming! I have passed the comments along to our survey administrators to see if updates can be made at this stage.

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [January 27, 2026, 12:53pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/6 "2026-01-27T12:53:16Z")

</div>

Yeah, I found quite a few of the questions unanswerable yet mandatory, and gave up on filling out the survey.

---

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [January 27, 2026, 1:22pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/7 "2026-01-27T13:22:05Z")

</div>

I did finish the survey, but I definitely felt that it had a number of preconceived assumptions that meant I was pushed into giving answers that didn’t really reflect my views, or falling back on “no opinion” rather than answering in a way that would be misinterpreted.

And while a lot of the questions had an “Other” option, I tend to find that it’s very rarely actually _helpful_ in capturing other views - there’s an implication that you’ll fill the text box with a short answer, like the other ones available, but often that’s not what you want. For example, given a question where over 50% of the options are AI-related, there’s no good 2-word “Other” choice that expresses the view “Why are you focusing so heavily on AI use cases, there’s a whole bunch of nuanced choices in other areas like process automation, and I would have selected 3 of those if they had been available”.

One other thing I found difficult to answer was a few questions which were framed as “Have you heard of these things”. I don’t see how that is useful. I’ve heard of a significant number of the AI services mentioned in one of the questions, for instance. But I have no interest in most of them, would never use them, and only know of many of them from news articles saying things like “here’s another over-priced AI service that the average developer can’t afford”. How is the fact that I’ve heard of these things of any use to anyone? And how will my saying that I’ve heard of them be _interpreted_? “Most Python programmers are up to date on developments in AI”???

---

<div class="post-metadata">

**Author:** ![alexprengere](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/alexprengere/32/5274_2.png) [@alexprengere](https://discuss.python.org/u/alexprengere)\
**Post date:** [January 27, 2026, 2:14pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/8 "2026-01-27T14:14:21Z")

</div>

On top of what has already been said, the question about “which test framework do you use: pytest/tox/unittest” made little sense to me, as tox does not operate as the same level as pytest/unittest (tox is the runner, takes care of venv creation etc.).

---

<div class="post-metadata">

**Author:** ![bwoodsend](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/bwoodsend/32/4027_2.png) [@bwoodsend](https://discuss.python.org/u/bwoodsend)\
**Post date:** [January 27, 2026, 10:06pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/9 "2026-01-27T22:06:34Z")

</div>

I’m still wishing for that _“I can’t answer this question without being misinterpreted”_ option. Every year that single-choice _“What python version do you use the most”_ question comes around and every year I have to pick at random because it doesn’t make sense. I develop libraries. They have to be compatible with a range of versions. Whilst `pyenv global` needs to be set to something, it’s picked on a whim and not even the same on my different machines/partitions.

It was quite depressing reading JetBrains’s blog post analysing last year’s survey results, made up of _exclusive insights_ and _action items_ based on questions that I and I suspect many others had to answer at random. Whilst the no-answer responses don’t do much to represent those that give them, at least they quantify how accurate or representative a given question is.

---

<div class="post-metadata">

**Author:** ![guido](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/guido/32/21_2.png) [@guido](https://discuss.python.org/u/guido)\
**Post date:** [January 27, 2026, 10:22pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/10 "2026-01-27T22:22:17Z")

</div>

Honestly if you develop Python itself or a key library or tool, this survey is not for you. I gave it up years ago.

---

<div class="post-metadata">

**Author:** ![BrenBarn](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@BrenBarn](https://discuss.python.org/u/BrenBarn)\
**Post date:** [January 28, 2026, 7:34am UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/11 "2026-01-28T07:34:11Z")

</div>

Last year\[1\] the following issues were raised in [this thread](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049), along with my perception of how the current survey stacks up with that past feedback.\[2\]

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/9):
>
> Are these questions really representative of what the PSF want to know?
> 
> I see a couple of boilerplate experience and background questions then the rest is almost exclusively what IDE you use, why you use that IDE, how you use your IDE, what tools/frameworks/databases/AI assistants/… (most of which PyCharm happens to have corresponding paid features for) do you use, what IDE features do you rely on…

The current survey seems to be the same.

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/10):
>
> Some of the multiple choice questions seem a little misguided. By tossing GUI frameworks, ML libraries, and data validation libraries (and only 2 of a much richer ecosystem of a couple of each of these) under the same category, it’s only going to validate what the survey asker seems to be aware of (at least, taking into account the issues with handling “other” in surveys)

It does seem that some categories of tool were broken out into separate questions this time, generally as sub-questions if you answered yes to “do you do Task X”.

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/12):
>
> brainstorming questions relevant to the various topics here (e.g. a section on typing (although there was that typing survey), about async, about packaging, etc…)

I didn’t see any such outreach happening on this forum. (The User Success WG was also mentioned but I don’t know what if anything happened on that front.)

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/15):
>
> The other, perhaps more controversial suggestion I would have is to have more questions that are about _opinions_ rather than “facts” like “what IDE do you use”.

I didn’t see any increase in such questions this year.

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/16):
>
> A small example [of a problematic question]:
> 
> ![image](https://us1.discourse-cdn.com/flex002/uploads/python1/original/3X/2/c/2c0a91c1eaf573715b1021bee22eb35d61d988a6.png)
> 
> For me, teaching Python for years, this question made no sense and didn’t have a “doesn’t apply” option.

This question still is there, still is mandatory, and still has no clear answer for people whose Python work is not clearly classifiable in terms of “professional” status. As other comments on this thread have indicated, the same seems to be true of many other questions in the survey. Sometimes there is an “other” option but almost all the questions are mandatory for no clear reason.

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/18):
>
> I’m not a fan of mandatory responses, period.

As mentioned, virtually all the questions are mandatory.

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/21):
>
> Can you share the survey questions and answers to translate it to other languages?

I didn’t see that happen on the other thread or elsewhere on this forum.

'll echo a comment from last year:

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/9):
>
> I’m trying not to sound conspiratorial but this current survey feels like marketing data for JetBrains rather than something to benefit the Python community.

The fact that so many of the issues discussed last year seem to have been duplicated this year, with no apparent outreach taking place in this forum, only exacerbates this problem.

@riecatnor, can you clarify what the benefit of this survey is supposed to be to the PSF and/or the larger Python community? I hate to say it but at this point I don’t really see it. There is a great opportunity here to make a survey that actually gathers input on questions that people spend a lot of time discussing, and this survey misses pretty much of all of that in favor of popularity-contest questions that smack of marketing research for JetBrains. Last year you said:

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/20):
>
> This brings me to the topic of JetBrains running the survey- I’m hearing that folks don’t _love_ the idea of providing free market research for JetBrains, which, makes sense to me. I am sure they are getting something out of it. On the other hand, if they didn’t run the survey for us, it probably wouldn’t be run.

Again, I hate to say this, but at this point I feel like it might actually be better to just tell them they can do it on their own if they want to, because, at least from my perspective, attaching the PSF’s imprimatur to this suggests a level of involvement in and relevance to the Python community that isn’t borne out by what the survey actually is.

* * *

1. or rather in 2024 — I gather there was no 2025 survey because of the change in launch date? 

2. I’m quoting the people who made comments in the other thread but obviously my perception of the current study in relation to those comments is my own and the people I’m quoting might not agree with me; just want to make that clear 🙂

---

<div class="post-metadata">

**Author:** ![riecatnor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/riecatnor/32/15602_2.png) [@riecatnor](https://discuss.python.org/u/riecatnor)\
**Post date:** [January 28, 2026, 7:18pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/12 "2026-01-28T19:18:24Z")

</div>

Thanks for the continued feedback here.

As I understand it, the current intended purpose of the survey is to provide data on the use of the Python programming language by developers for the entirety of the Python ecosystem. I saw many write ups about the last survey’s results, and a few that were shared very broadly, and I’ve also seen community professionals comment that they refer to the data yearly. So, I think it is at least somewhat useful for some groups and people in the broader Python ecosystem. I think what folks are saying here is that it doesn’t feel very useful for individual/core community members as it stands (if I am misunderstanding, please let me know)- and if that’s correct, I agree that needs to be addressed.

I have flagged this with the PSF Board for their review and direction for future. Noting that because the Board is made up of a group of volunteers located across time zones (with plenty of additional and urgent matters to address), I don’t think changing the direction of this years survey is possible.

So, my follow up question to the folks/community on this thread and beyond: What data would you find useful to collect and analyze? Are there any parts of the survey results that are typically useful to you? What processes would you like to see around the implementation of a survey?

---

<div class="post-metadata">

**Author:** ![bwoodsend](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/bwoodsend/32/4027_2.png) [@bwoodsend](https://discuss.python.org/u/bwoodsend)\
**Post date:** [January 28, 2026, 8:08pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/13 "2026-01-28T20:08:25Z")

</div>

> [@riecatnor](#):
>
> So, I think it is at least somewhat useful for some groups and people in the broader Python ecosystem. I think what folks are saying here is that it doesn’t feel very useful for individual/core community members as it stands (if I am misunderstanding, please let me know)- and if that’s correct, I agree that needs to be addressed.

That and the frustration at having to give answers that aren’t true because of the limitations of multiple choice. If community professionals are making decisions based on these results then they are probably ill-informed decisions.

> [@riecatnor](#):
>
> What processes would you like to see around the implementation of a survey?

Would it be possible to trial the survey on little groups before going live and ask them which questions they felt they couldn’t answer?

It also might help if the intention behind each question was public. If we had some idea as to why a question is being asked, we could help turn it into a more meaningful question. \[1\]

* * *

1. … and maybe some of the marketing research for PyCharm integrations would become slightly less brazen…

---

<div class="post-metadata">

**Author:** ![brass75](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brass75/32/19784_2.png) [@brass75](https://discuss.python.org/u/brass75)\
**Post date:** [January 28, 2026, 8:13pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/14 "2026-01-28T20:13:41Z")

</div>

It felt more like a survey about IDEs than about how people use Python and what matters for that. I will also say that asking about my hobbies is completely irrelevant. Finally, there was a distinct lack of focus on open source contributions as a major use of Python - it seemed all about professional and not beyond.

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [January 28, 2026, 8:17pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/15 "2026-01-28T20:17:16Z")

</div>

> [@brass75](#):
>
> It felt more like a survey about IDEs than about how people use Python and what matters for that.

Well, yes. It’s a JetBrains survey. 🙂

---

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [January 28, 2026, 10:23pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/16 "2026-01-28T22:23:10Z")

</div>

That’s definitely an option. I considered it this year. But frankly, people make decisions based on the results of this survey, and I’m not happy at the thought of my usage not being represented in those decisions.

Call me naïve, but I’d like to do my small bit to remind people that not everyone using Python wants to go all in on AI…

---

<div class="post-metadata">

**Author:** ![BrenBarn](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@BrenBarn](https://discuss.python.org/u/BrenBarn)\
**Post date:** [January 29, 2026, 5:56am UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/17 "2026-01-29T05:56:36Z")

</div>

> [@riecatnor](#):
>
> I saw many write ups about the last survey’s results, and a few that were shared very broadly, and I’ve also seen community professionals comment that they refer to the data yearly. So, I think it is at least somewhat useful for some groups and people in the broader Python ecosystem.

Can you clarify in what way you think (or have heard) it is useful? In last year’s thread you said:

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/20):
>
> I’ve seen a handful of dedicated blog posts on the most recent survey results([1](https://techhq.com/2024/09/python-developer-opportunites-will-continue-as-world-demands-ai-and-ml/), [2](https://socket.dev/blog/packaging-trends-in-python-highlights-from-the-2023-developer-survey), [3](https://thenewstack.io/25000-python-devs-surveyed-on-tools-ides-and-python-2/), [4](https://www.i-programmer.info/news/216-python/17536-be-counted-in-the-python-developer-survey.html)), I’m sure there’s more I haven’t seen, and I coordinated a [live stream event with JetBrains](https://www.youtube.com/live/GPwYSf1t8Lw?si=9Fur9sFhMwXvXx_T) to discuss the results (which has 6K+ views). Based on all that, I’d like to think the survey is useful beyond market data for JetBrains.

I want to push back a bit on that framing. Personally, I do not see those four articles as evidence that the survey is useful in any way. All of them seem to consist entirely of restatements of some subset of the results in a prose format. I searched the web for analyses of the survey data and found basically more of the same. The mere fact that people tell other people that the survey was done and got certain numbers doesn’t tell us much about whether any of it was meaningful.

> [@riecatnor](#):
>
> What data would you find useful to collect and analyze? Are there any parts of the survey results that are typically useful to you? What processes would you like to see around the implementation of a survey?

The main issue I see is that more or less this same question was asked last year, and yet this year’s survey appears to have incorporated very little of that feedback, nor was there (to my knowledge) any public process on this forum\[1\]. In addition, last year you said:

> [@Python Developers Survey 2024 is now open: respond and share!](https://discuss.python.org/t/python-developers-survey-2024-is-now-open-respond-and-share/67049/20):
>
> In response to @BrenBarn’s question regarding the current survey design process: we have a chance to review the questions in advance (PSF Staff, PSF Board, & other community folks we invite) and we can suggest edits or additions.

This phrasing suggests that the survey is basically designed in private by JetBrains and the PSF merely “reviews” and “suggests” changes. Is that correct? Can you say explicitly what the survey design process is?

My personal view is that there is not much point in the PSF attaching its name to such a survey. What would be useful is a flip of that, in which some group of community members\[2\] designs the survey with public input. In other words it sounds like right now this is fundamentally a JetBrains survey to which the PSF’s name is attached; I don’t see much use to it unless it is going to be fundamentally a PSF survey that JetBrains merely administers.

* * *

1. or anywhere else, as far as I can tell with web searches 

2. e.g., members of the PSF, members of working groups, noted Python teachers or developers, people involved Python’s governance

---

<div class="post-metadata">

**Author:** ![tim.one](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/tim.one/32/282_2.png) [@tim.one](https://discuss.python.org/u/tim.one)\
**Post date:** [January 29, 2026, 6:48am UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/18 "2026-01-29T06:48:12Z")

</div>

Like Guido, I don’t participate in these surveys. They’re not looking for what people who work _on_ Python think or do, but on what people who _use_ Python do. And it appears to be useful to many for that purpose. Read what they said about the results of a recent survey:

> **[The State of Python 2025: Trends and Survey Insights | The PyCharm Blog](https://blog.jetbrains.com/pycharm/2025/08/the-state-of-python-2025/)**
>
> Learn what 30,000 developers say about Python in 2025. Discover the latest survey stats, usage trends, and predictions to stay ahead in the Python world.

I do read, and appreciate, these summaries of survey responses. They say a lot about where Python is and may be heading. Like how very many Python users are relatively inexperienced programmers, and how heavily “data science” has come to dominate applications. Although reconciling those two is a bit of a puzzle for me 😉

No doubt some of this is driven by JetBrains’s own marketing efforts. That’s fine by me too. Python has always tried to cooperate with companies seeking to serve (& profit from) the Python programming community, and doing so is thoroughly in line with the PSF’s mission statement.

But, regardless, surveys are always annoying to fill out 😉

---

<div class="post-metadata">

**Author:** ![UltimateLobster](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ultimatelobster/32/9727_2.png) [@UltimateLobster](https://discuss.python.org/u/UltimateLobster)\
**Post date:** [January 29, 2026, 6:54am UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/19 "2026-01-29T06:54:10Z")

</div>

Considering this is a survey that is supposed to be useful to the Python community, I would like to have an opportunity to provide feedback on the language itself: Aspects of the language that I like/dislike and what direction I’d like to see the language go.

It would be cool if the survey gave people a chance to provide meaningful feedback on recent Python features:

How often do people use a particular recent feature? Did it become more popular throughout the years? Do people like/dislike the feature?

What about upcoming features? Are people excited for a specific thing in the next python version?

Another problem I have is that despite the survey’s focus on IDEs, I don’t even feel like I get to provide feedback on the IDEs themselves. I didn’t feel like the survey gave me a good way of communicating which exact aspects of my IDE I like/dislike.

In summary:

- I’d like to see questions relating to the language itself.
- I don’t mind questions about IDE’s, but the major focus should be the language itself.
- If we have questions regarding IDEs, I’d like to see a way to provide more meaningful feedback on the IDE of my choice.

---

<div class="post-metadata">

**Author:** ![villares](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/villares/32/12349_2.png) [@villares](https://discuss.python.org/u/villares)\
**Post date:** [January 29, 2026, 12:39pm UTC](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883/20 "2026-01-29T12:39:37Z")

</div>

Thank you @BrenBarn for articulating this so well. I have been complaining about the survey for many years now. I feel terrible for not being able to act on this in an effective way.

It is frustrating that almost no feedback at all was incorporated, the survey does very little for understanding the diversity of Python users, it is specially bad at surveying folks outside the conventional professional development circles and IDE users that JetBrains is focused at.

A working group and public inputs sounds essential. I believe we should also reach out for people who work with surveys for scientific research, there are people out there who know how to design and run good surveys, reduce [self-]selection bias, etc. Ideally, I wish we could have kind of a “census” of Python users, having people actively trying to find where the Python users are and what are they using it for. Paraphrasing Sumana Harihareswara on the challenge that is to reach _pip_ users (I hope I’m not distorting it too much from the very inspiring Pycon 2024 keynote): '“Everyone drinks water, but very few think of themselves as ‘water users’ and sign up for the ‘water newsletter’”. The same goes for Python as a whole. Isn’t the PSF message “Python is for everyone”?

[Next page](https://discuss.python.org/t/your-python-your-voice-join-the-python-developers-survey-2026/105883.md?page=2)
