pyRevit - 2025 Year in Review Link to heading
2025 was a year of consolidation, technical progress, and growing contributor momentum for pyRevit.
Across releases, pull requests, and forum discussions, the project continued to mature while welcoming new contributors and laying the groundwork for the next major platform transition.
🚀 Product Progress & New Features Link to heading
2025 delivered a steady stream of improvements across the pyRevit 5.x series — not just compatibility work, but real workflow upgrades and tooling polish.
Notable highlights from the year include:
- Continued stability and compatibility improvements for Revit 2025
- Numerous tool refinements and bug fixes driven by production feedback
- Quality-of-life improvements around printing, exporting, progress reporting, and crash prevention
- Improvements to CLI workflows, installer behavior, and runtime handling
- Ongoing cleanup and modernization of internal structure to support future platform changes
Community-contributed features and fixes played a major role, including:
- New and enhanced tools such as Measure 3D improvements, Sectionbox Navigator, Relink Textures, and other usability-focused updates
- Community extensions like pyrevit-mcp by @JotaDeRodriguez and the Quickly Toolbar extension by @tay0thman
- Important fixes and maintenance work credited to contributors such as @thumDer
- A key panelbutton bug fix credited to @Wurschdhaud, which helped set the quality bar for the 5.3.1 release
Rather than one single headline feature, 2025 was defined by cumulative quality gains that made pyRevit more robust, predictable, and maintainable.
🧩 Major Technical Work: The New C# Loader Link to heading
One of the most significant efforts underway in 2025 is the new C# loader, which is now very close to completion.
- The loader is entirely cooked by @romangolev
- It modernizes pyRevit’s startup and integration layer
- It lays the foundation for better performance, maintainability, and future Revit compatibility
This work represents a major architectural step forward and will be foundational for upcoming releases.
👥 Growing the Contributor Base (with Shout-Outs) Link to heading
2025 also stood out for the breadth of contributors helping pyRevit move forward — through code, reviews, fixes, and community support.
Shout-outs to contributors credited throughout 2025 releases and updates:
- @Wurschdhaud — great newcomer with impactful fixes
- @romangolev — major architectural work (C# loader)
- @tay0thman
- @MohamedAsli
- @Isaiah-Narvaez-42
- @WemyssJ
- @ramyamaher
- @Swichllc
- @thumDer
- @nasmovk
- @Denver-22
- @czwangxtt
- @frank-e-loftus
- @IGF-Zhang
- And the “usual suspects in the background”: @sanzoghenzo and @dosymep
If we missed a drive-by contributor who shipped a fix, reviewed a PR, or helped on the forum — thank you. The project is stronger because of your involvement.
💰 Open Collective — 2025 Financial Overview Link to heading
All funding and expenses are transparently tracked via Open Collective.
Below is the verified summary for calendar year 2025, based strictly on recorded transactions.
📊 Summary Link to heading
| Category | Amount (USD) |
|---|---|
| Total Contributions | $3,185.00 |
| Total Expenses | −$3,020.67 |
| Net Result | +$164.33 |
💸 Expenses by Purpose Link to heading
| Purpose | # Transactions | Total (USD) |
|---|---|---|
| Maintenance & Development | 4 | −$1,133.73 |
| Travel (community & events) | 2 | −$880.15 |
| Hosting & Subscriptions | 16 | −$713.57 |
| Advertising & Marketing | 1 | −$293.22 |
| Total Expenses | 23 | −$3,020.67 |
Most funds were reinvested directly into development, contributors, and essential infrastructure, keeping pyRevit sustainable and moving forward.
🔭 Looking Ahead: The Next Challenge Link to heading
The next major technical milestone is already clear:
- Migrating to .NET 10
- Ensuring full compatibility with Revit 2027
This transition will be critical for pyRevit’s long-term future and will require:
- Continued architectural work
- Thorough testing across Revit versions
- Time and focus from experienced contributors
🤝 A Note to Sponsors & Supporters Link to heading
pyRevit remains free and open-source, but it is not free to build or maintain.
Your financial support helps:
- Fund maintenance and new feature development
- Support contributors doing deep technical work (like the new C# loader)
- Cover infrastructure, tooling, and community costs
- Lower the barrier for new contributors to get involved
If pyRevit saves you time, enables automation, or supports your team’s workflows, please consider supporting the project financially:
👉 https://opencollective.com/pyrevitlabs
Even small recurring contributions make a real difference — and directly support the people building the tools you rely on.
Thank you to everyone who contributed in 2025 — through code, discussions, testing, funding, or support.
Here’s to an ambitious and exciting 2026. 🚀
any mistakes? blame chatgpt! :devil: