The nitty gritty of Concurrency for Python

On October 14, aside from lightning talks from our members, let's dig into the nitty gritty of concurrency for Python. Please sign up to give a lighting talk here (https://docs.google.com/forms/d/1LtV839ktupRboMUSXlXqoJ9lLFvpe-TZtLCf2q6jUpY/viewform?usp=send_form).

Talk #1 An introduction to Vanilla: Straightforward concurrency for Python

Abstract:

Vanilla allows you to build concurrent software in Python. Vanilla programs are structured around independent coroutines (greenlets) which communicate with each other via Pipes. Pipes are similar to channels in Go programming.

There's no callback crazy-ness and no monkey patching. Vanilla strives to be as explicit and straightforward as possible.

'If Go and ZeroMQ had a baby, and that baby grew up and started dating PyPy, and they had a baby, it might look like Vanilla.'

https://github.com/cablehead/vanilla

http://vanillapy.readthedocs.org/en/latest/

Bio:

Andy Gayton has extensive experience building custom software stacks for high throughput internet services, including video streaming (Revver), social gaming (Slide, Lolapps), realtime data synchronization (Simperium), messaging (MessageMe) and realtime image rendering (Imgix).

Talk #2 From Python to Go, and Back Again!

Abstract:

After 7 years of using Python for almost all projects both at home and professionally, Ben dived into learning Go 1.0 in 2012. Armed with the power of static typing, speed, and powerful concurrency features it seemed like Go was the answer to many of the problems that arise in server-side network software he was faced with daily.

The first project was heka, a message parsing/processing tool used at Mozilla and other companies to replace Logstash. Next was the new Push Service being deployed to service FirefoxOS clients. During this project, some interesting problems came up with Go, and Python returned to the big picture. Join us for the story of how and why this project, started in Go, transitioned to Python, and how its worked out since.

Bio:

Ben Bangert is known in Python open source community for his work in creating the Pylons web framework (http://www.pylonsproject.org/projects/pylons-framework/about), along with his work on other software libraries such as Routes (http://routes.readthedocs.org/en/latest/), Velruse (http://velruse.readthedocs.org/en/latest/index.html), Kazoo (https://github.com/python-zk/kazoo), and much more (https://github.com/bbangert). He is a PSF Member and works at Mozilla.

Agenda:

6:00p - Check-in and mingle, with Pizza and Beer provided by our generous sponsor Yelp!

7:05p - Welcome

7:10p - Lightning Talks and Announcements while lightning speakers set up

7:35p - Talk 1 and Q&A

8:20p - Talk 2 and Q&A

9:30p - Doors close

Lightning talks:

Mik Kocikowski - GNU make for easy parallelization of ETL in Python

Sebastien Mirolo - Python class inheritance and HTML wizards

Allison Nelson - Building a Modular Chatbot with the Errbot Framework

Please take note of the important check-in details at Yelp

1. Doors open at 6:15pm to allow enough time for the check-in process. Before 6:15pm, please wait outside without blocking the building entrance. Wait list will be admitted beginning at 6:45pm. Doors close at 7:30pm.

2. Please update the name on your account to reflect your FIRST NAME and LAST NAME. Yelp security will be checking IDs downstairs. If your name on Meetup.com is not the name on your ID, then please enter your full name here (https://docs.google.com/forms/d/1d_oPoxjcAQzOJqozHIzVuFNnOYi7CDrzouywq4U9SUo/edit).

3. Since alcohol will be served at the event, we ask that any underage attendees RSVP directly to the meet up organizers.

4. Waiting list folks will be allowed into the event AFTER we admit all confirmed attendees.

5. Unfortunately, Yelp cannot safe keep your bicycles, please park your bike on the street.

Yelp is generously providing food, drinks, and beer in addition to their venue space.