A resource for collecting and collating information around tools and best practices about what python constructs are compileable and how to actually compile python, practically in your project.
Think 'something like TripAdvisor for Python Compiler Tools', NOT 'yet another partial python compiler'
This repo and website is currently being bootstrapped.
Page history:
- Repo boostrapping - Feb 2026 (see the repo history)
- Last update 22/2/2026
Who am I? I'm Michael Sparks. I've been around the Python Community sometimes more involved, sometimes less for around 23, 24 years now. I helped found PyconUK back in the day, helped found Python Northwest (UK) back in the day, and also ran the Kamaelia project for many years.
I also created the original prototype technology behind the BBC micro:bit which now teaches python and coding and more across the world. The original prototype was more constrained than the current device, and to operate needed a constrained python to C++ compiler. I've also tinkered previously with a more generic python to C++ compiler called Pyxie. So I have a long standing interest in this area.
In recents months and years, I've become much more aware of the climate cost of software and technology and Green Computing is something that really matters to me. I'm interested in a number of ways of doing this. Green Computing however, includes things like new ways of encouaging sciences to effectively use hardware, performance engineering and again that brings us back to this project.
I've put myself on the hook to develop this site and resource, and to run the events around it via an SSI Fellowship. In practical terms, this helps with running events etc throughout this year - to help get this site bootstrapped.
I am grateful for feedback and and advice, and seeking out collaborators. Initially I'm taking advice from Steve Holden, whom I'm sure many in the python community will recognise.
From pages/index.md --
(text currently adapted from my pitch to the SSI)
Python is popular and and much slower than compiled languages like C++, Rust, etc. Combine those two, and you have a green compute problem weighted by popularity. Low performance means more energy. More energy means more CO₂.
CompilePython.com exists to address this
CompilePython.com is:
- A place for sharing problems and solving them
- A place to share what works
- A place to document what doesn’t
- A place to describe required subsets
- A place for real-world experience reports
- An incomplete Python compiler
- A silver bullet
- A marketing site
- It is for knowledge collation.
- Performance
- Sustainability
- Real-world engineering
- Community collaboration
The goal is credible, maintainable, lean-first documentation and experience sharing.
- Github: https://github.com/sparkslabs/compilepython
- Google Groups: https://groups.google.com/g/compilepython
- Mailing List:
- Send a blank email to mailto:compilepython+subscribe@googlegroups.com
- You will be asked to confirm your email - the simplest way is send a reply "OK" (especially if your mail provider rewrites emails)
- Discussions: https://github.com/sparkslabs/compilepython/discussions
CompilePython.com will run four Lightning Camps in 2026.
These are unconference / open space style events focused on:
- Real-world experience reports
- Compiler tool comparison
- Python language Subset mapping
- Sustainability implications
- What actually works
But they are also open to wider Python communities.
- March 2026 – Online Lightning Camp
- July 2026 – Online Lightning Camp
- October 2026 – In-person / hybrid Lightning Camp
- December 2026 – Online Lightning Camp
Each camp will:
- Be collaborative
- Be practical
- Produce artefacts
- Feed directly into the living guidebook
My belief is that python isn’t going away, that compiling Python is hard. Knowledge is fragmented and experiences are scattered. If it were easy, everyone would already be doing it. I also firmly believe that we solve hard problems by working together.
CompilePython.com is about making that collaboration visible, credible, and sustainable.
It's a journey with a number of many possible routes and destinations. It's why I thought of TripAdvisor as my initial analogy.
Code will be Apache 2 License by default.
Content will be Creative Commons CC-BY 4.0
I am very thankful for the sounding board and advice I've recieved so far from Steve Holden (Former PSF Chairman/Director etc)
Funding for community events and infrastructure comes from the Software Sustainability Institute via Michael's SSI Fellowship.
I am extremely thankful to those at the SSI who encouraged me to apply, helped me shape my proposal and helped me decide on this project as my target. I am also thankful for the funding that makes events and infrastructure possible.