I was able to attend my third PyCon this weekend in Santa Clara, CA.
Usually, I step through each talk that I’ve attended and document my thoughts. A large review post, really. High points and low points. I think I’m going to skip that this time around and concentrate on what has really become a bit of a reoccurring problem for me (no, not a real problem, don’t worry).
Each year I leave PyCon feeling pretty involved in the community. This usually means studying CPython code for a couple of weeks afterwards, fixing a small collection of bugs found on the issue tracker, and looking for a larger project. I’ve even contemplated sending in a contributor’s agreement such that I can submit changes back to the little interpreter that has been paying my bills for the past seven years.
Last year, for example, I implemented a “go” keyword — down to the byte code level — just to learn how things are wired up. It was quite a rewarding experience as I got to touch areas of the codebase that usually simply annoy me with cryptic errors.
But, time and time again, I wind up burning out after not finding anything substantial to contribute back. There does seem to be quite a push to get new “core developers”, though I’m not sure where to jump on in. For example, the following resources are wonderful:
- The Developer Guide outlines the need for submissions and mentor programs.
- Mr Hasting’s talk on Stepping Through CPython.
I’m fairly determined to avoid that crash this time through by simply asking. Python world, who wants help? Is there still a need for new people on the CPython proper? Or, have we largely hit critical mass there? Would time be better spent on a third party component? Standard library improvements? Is it worth mailing in that contributor agreement in hopes of finding something worthwhile to chip away at?
In: development, open source, pycon, python