As the PSF heads into our end-of-year fundraiser this month, we want to “connect the dots” and share a full picture of our current financial outlook: what’s happening, why, and how you can help sustain the future of Python and the PSF. 🧵
https://pyfound.blogspot.com/2025/10/connecting-the-dots.html
Over the past year+, we’ve shared updates on things like the Grants Program pause, PyCon US financial transparency, our NSF grant withdrawal, and the “Open Infrastructure is Not Free” statement. This new post pulls those threads together into one clear overview.
In short: our costs have gone up, our assets and revenue have gone down, and demand for the PSF’s work continues to grow. Meanwhile, Python usage is surging (which is great!), but corporate investment in the language and community hasn’t kept pace.
When we shared last week that we withdrew from a U.S. government grant due to conflicts with our mission, the community showed incredible support. 1400+ donors and 270+ new members raised $135K+ in solidarity– thank you!! We've also had 3 new companies apply for sponsorship 🤯🥰
Should the PSF continue to sustain PyCon US directly?
It’s the flagship Python event, but it also seems to consume a large portion of PSF funds with limited benefit for the global community.
Wouldn’t it make more sense for PyCon US to rely more on external sponsorships and partnerships, instead of drawing so much from the PSF itself?
Also, how much support do regional PyCons receive by comparison?
Read the full post to see how the PSF is tackling these challenges and how you can help power the future of Python. Many of you have donated in the past week- so we are looking for you to help us with reach. Please share this story, boost our upcoming fundraiser posts, and most importantly, tell the world your #Python story!
This is a bonfire demo instance for testing purposes
