Skip to main content

PyCon 2012 News - Tutorials, Talks, and Tickets

The following was an email sent to all known Python local user groups -- a list totaling 108 locations around the world. If you're in a user group and *haven't* seen this information, please email brian@python.org or comment on the post if your group would be interested in receiving this type of "newsletter" format. We don't send them often and we won't spam you, we just want to reach the community for which PyCon exists to serve.


We are now 63 days away from PyCon 2012 in Santa Clara — it's hard to think about how quickly time has flown since PyCon 2011! We've lined up some great keynote and plenary speakers, announced the tutorial and talk selections, opened ticket sales, and have expanded financial aid opportunities. The community and our amazing array of sponsors have helped us break several records already, so we hope you're as excited about PyCon 2012 as we are. The conference runs March 7-15 at the Santa Clara Convention Center in Santa Clara, CA.


The keynote speakers include Y Combinator investor Paul Graham and Mozilla's Head of Developer Engagement, Stormy Peters. Both of them bring interesting experience to the table, and they're both captivating speakers. Speaking of captivating, Dave Beazley was announced on the plenary track, with more to be added in the coming weeks. Guido — our Benevolent Dictator For Life — will also be joining the line up!



With 483 tutorial, talk, and poster proposals submitted this year, the program committee had their hands full paring that list down to 95 talks, 32 tutorials, and 36 posters (which we're still accepting). In the little time since we made these announcements we've heard a lot of excitement. You can see the tutorial selections at https://us.pycon.org/2012/schedule/lists/tutorials/, with talks available at https://us.pycon.org/2012/schedule/lists/talks/.



Tickets are now available with early bird rates available until January 25, 2012 at https://us.pycon.org/2012/registration. Tutorial and admission prices continue unchanged; if you've been following along the last few years, these rates are the same as they have been for several years. Our team's dedication to keeping PyCon cost-effective, community driven, and grassroots continues thanks to the hard work and support of the team and sponsors (https://us.pycon.org/2012/sponsors/).



If financial assistance would make PyCon a possibility for you, we encourage you to apply to this year's expanded assistance program. With a deadline of January 7, 2012 (extended from January 2) and a new web-based application, the financial aid committee aims to make the trip, lodging, and a ticket a possibility for everyone. Thanks to a new partnership with the PyLadies organization, we're able to provide grants to women in the community who are interested in experiencing the conference. For full details see https://us.pycon.org/2012/assistance.



For more information about PyCon 2012, see our site at https://us.pycon.org/2012/. We also publish news on our blog: http://pycon.blogspot.com/.



Jesse Noller - Chairman

Brian Curtin - Publicity Coordinator

Comments

Popular posts from this blog

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…