PyOhio 2014, the annual Python programming conference for Ohio and the surrounding region, will take place Saturday, July 26th, and Sunday, July 27th, 2014 at The Ohio State University in Columbus, Ohio.
You can read more about the conference at http://pyohio.org. If you have questions about proposals, please email firstname.lastname@example.org. You can also contact the PyOhio organizers at email@example.com.
PyOhio invites all interested people to submit proposals for scheduled talks, tutorials, and panels. All topics of interest to Python programmers will be considered. Standard presentation talk slots will be 40 minutes plus a 10 minute question-and-answer period. Tutorial slots will be 110 minutes long.
Who Should Submit a Proposal?
You. Your friends. Your friends' friends. Anyone with any level of Python knowledge is a candidate for a great topic at this conference. As we get attendees of all kinds, we need speakers of all kinds. In all ways and manners, we try to assemble the most diverse conference we can, and we do that with your help.
Whether you got started with Python last month or you've been around for 20 years, we think you've got something to share. The Python community is stronger than ever and we're still reaching new areas, new industries, and new users. Be a part of growing Python by helping us change the future.
Send in your proposals before May 1st, 2014!
In particular, we welcome submissions from people that have never done a talk before! And if you want help preparing a talk, let us know! Volunteers are eager to help new people do talks.
You can submit more than one proposal.
Example topic ideas
Do you want to work on a talk, but don't have any ideas? The topics below are up for grabs. Several people could easily work together on each one. Please take these ideas and stretch it out or focus on just one part of it or do whatever else you want.
Parallelism shootout: threads vs multiple processes vs libevent
Here's a pretty common puzzle: you need to download data from lots and lots of URLs stored in a text file and then save that data to a database.
Sure, you could write a loop and get each URL in sequence, but imagine that there are so many URLs that the sun may burn out before that loop finish. Or you're just too impatient.
For the sake of making this instructive, pretend you can only use one box.
So, what do you do? Here are some typical solutions:
- Use a single process that creates lots of threads.
- Use many processes.
- Use a single process and a library like gevent or eventlet to yield between coroutines when the OS blocks on IO.
The talk will walk through the mechanics of each approach, and then show benchmarks of the three different approaches.
This talk would be a great opportunity to study the heck out of these systems and then construct some meaningful benchmarks.
Walk through porting a library from python 2 to python 3
A lot of us are staying on python2 even though python3 is better in a million ways. Usually this is because we depend on packages that don't work in python3 yet.
Check out the Wall of Superpowers for a list.
Show us how to fix these packages! Walk through generally what is involved in porting a package. Show us how to install many different versions of python and how to write and run tests to verify a package on all those.
Describe what work was done to port a particular package (or maybe several packages) that have been ported over.
This could lead to some really good sprints!