We have many concurrency/multiprocessing capabilities at our finger tips, such as threads, processes, locks, mutexes, select, epoll, transactional memory, etc. But none of them are a model for multiprocessing, they are only tools on which you would build an implementation of such a model. So what are the models we can choose from? How would they be implemented in Python? And how do they relate to the principle of sufficient irritation?
Joe Gregorio is a software engineer working on APIs at Google. He is a member of the AtomPub Workgroup, editor of the Atom Publishing Protocol, co-author of the URI Templates spec, and has a deep interest in web technologies, writing “The RESTFul Web” column for the online O’Reilly publication XML.com, writing the first desktop aggregator written in C#, and publishing various Python modules to help in putting together RESTful web services such as mimeparse, httplib2, and the google-api-python-client. He’s interested in REST, web services, Python, APIs, URI Templates, Atom Publishing Protocol, Big Data, or any linear combination of such.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at scordesse@oreilly.com
Download the OSCON Sponsor/Exhibitor Prospectus
Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the OSCON Newsletter (login required)
Have an idea for OSCON to share? oscon-idea@oreilly.com
View a complete list of OSCON contacts
Comments
Joe, any chance you’d be willing to post the slides from your talk?
Thanks!
Michael
I thought the presenter made a good point that if there are design patterns, the language is missing something, and he showed how threading was one such case. I thought there could have been more material though.
Dirk, Sorry you were disappointed with the talk. If I give it again I will definitely update the description to make the scope of the talk clearer.
I was very disappointed with this talk. I expected to learn something substantive about concurrent programming in python, and instead I got a long winded discursion about pretty much everything but.