audience-instructors for Teach Me Python Bugfixing needed
Hey, everybody... I'm Catherine, a database administrator who makes up excuses to write Python instead.
I'm not actually here as a core developer, but as somebody who hopes to become a developer and recruit some more, which brings me to my question:
Who lives close enough to Ohio to make it to PyOhio this summer? I want to use PyOhio to create new Python devs (including myself), but I need some existing ones to seed the process.
I need a few veterans (3?) who can commit to come to PyOhio and take part as audience/instructors in a "Teach Me [Python core / standard library] Bugfixing" session. (See http://catherinedevlin.blogspot.com/2010/04/bugfixing-at-pyohio.html.) The PyOhio Call for Proposals is up May 10 so I'd better find you quick!
I'm pretty much ignorant enough to lead a Teach Me session. In a Teach Me session, the person at the projector *doesn't* know the material. Instead, she asks the audience questions ("How do I find a bug to work on?"), and they talk her through it. It's based on Teach Me Twisted, a mind-blowing session Steve Holden led at PyCon 2008 ( http://catherinedevlin.blogspot.com/2008/03/teach-me-twisted.html). I think it's a fantastic way to teach, but it depends on some veterans being in the audience. There are folks in the greater Python community eager to get hold of a video of such a session... if we do this well, it could become an important tool in keeping the quality of core Python code high.
And all I need from you, my audience-instructors, is a promise to show up (no preparation necessary). Can you make it? Can you pass the appeal on to others you know of?
Thanks! Hope to see you in July!
What an excellent idea! We should have these at *every* regional conference.
Doug
On May 6, 2010, at 10:47 AM, Catherine Devlin wrote:
Hey, everybody... I'm Catherine, a database administrator who makes up excuses to write Python instead.
I'm not actually here as a core developer, but as somebody who hopes to become a developer and recruit some more, which brings me to my question:
Who lives close enough to Ohio to make it to PyOhio this summer? I want to use PyOhio to create new Python devs (including myself), but I need some existing ones to seed the process.
I need a few veterans (3?) who can commit to come to PyOhio and take part as audience/instructors in a "Teach Me [Python core / standard library] Bugfixing" session. (See http://catherinedevlin.blogspot.com/2010/04/bugfixing-at-pyohio.html.) The PyOhio Call for Proposals is up May 10 so I'd better find you quick!
I'm pretty much ignorant enough to lead a Teach Me session. In a Teach Me session, the person at the projector *doesn't* know the material. Instead, she asks the audience questions ("How do I find a bug to work on?"), and they talk her through it. It's based on Teach Me Twisted, a mind-blowing session Steve Holden led at PyCon 2008 (http://catherinedevlin.blogspot.com/2008/03/teach-me-twisted.html ). I think it's a fantastic way to teach, but it depends on some veterans being in the audience. There are folks in the greater Python community eager to get hold of a video of such a session... if we do this well, it could become an important tool in keeping the quality of core Python code high.
And all I need from you, my audience-instructors, is a promise to show up (no preparation necessary). Can you make it? Can you pass the appeal on to others you know of?
Thanks! Hope to see you in July!
--
- Catherine
http://catherinedevlin.blogspot.com/ *** PyOhio 2010 * July 31 - Aug 1 * Columbus, OH * pyohio.org *** _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/doug.hellmann%40gmail.com
Hello,
Who lives close enough to Ohio to make it to PyOhio this summer? I want to use PyOhio to create new Python devs (including myself), but I need some existing ones to seed the process.
I'm not really answering your question (I'm very far from Ohio), but a good way to start up without physically meeting a core dev in your area would be to look for bugs in the issue tracker and start tackling those that tickle your interest. "Tackling" here can mean proposing a patch, or giving advice, or asking for guidance on how to produce a patch for that particular issue, or even reviewing an existing patch. You don't have to be a CPython expert to try this; just be prepared to spend some time exchanging with other people who will point out possible mistakes, or teach you some of the annoying idiosyncrasies.
Scanning through open issues will also give you a general idea of what kind of functionalities are looking for improvement, or need fixing.
(you can create a new issue and start tackling it yourself, too)
Also, if you have enough free time, you can hang out on #python-dev, which can speed up the process, but it's not required.
You can also find formal information about the development process here: http://www.python.org/dev/faq/
Regards
Antoine.
On Thu, May 6, 2010 at 9:29 AM, Antoine Pitrou solipsis@pitrou.net wrote:
Scanning through open issues will also give you a general idea of what kind of functionalities are looking for improvement, or need fixing.
(you can create a new issue and start tackling it yourself, too)
As a wanabe Dev I think the hardest thing is to find an open issue I can
actually fix and to have a mentor to help make sure I don't miss something I did not know about.
Please record the "Teach Me" session if it happens. (audio and/or video)
*Vincent Davis 720-301-3003 * vincent@vincentdavis.net my blog http://vincentdavis.net | LinkedInhttp://www.linkedin.com/in/vincentdavis
Vincent Davis wrote:
As a wanabe Dev I think the hardest thing is to find an open issue I can actually fix and to have a mentor to help make sure I don't miss something I did not know about.
Does the "easy" tag help with that at all? It's intended to mark issues that aren't delving into deep dark corners of the interpreter or standard library, but when you've been doing this for a long time one's judgment of what's easy and what's difficult can get a little askew.
(e.g. I recently marked the task of fixing the enumerate docstring as easy, but that does still require knowing how docstrings work for C code)
Cheers, Nick.
participants (5)
-
Antoine Pitrou -
Catherine Devlin -
Doug Hellmann -
Nick Coghlan -
Vincent Davis