[From nobody Sat Mar 13 18:15:09 2010 Return-path: <webmaster@us.pycon.org> Envelope-to: tismer@stackless.com Delivery-date: Mon, 19 Nov 2007 01:44:58 +0100 Received: from rampart.timecastle.net ([192.67.63.145]) by chewwy.tismer.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.67) (envelope-from <webmaster@us.pycon.org>) id 1Itul0-0002GL-0w for tismer@stackless.com; Mon, 19 Nov 2007 01:44:58 +0100 Received: from rampart.timecastle.net (localhost [127.0.0.1]) by rampart.timecastle.net (Postfix) with ESMTP id 21FDF2C039 for <tismer@stackless.com>; Sun, 18 Nov 2007 18:37:37 -0600 (CST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: PyCon 2008 Talk Proposal Submission From: webmaster@us.pycon.org To: tismer@stackless.com Date: Mon, 19 Nov 2007 00:37:37 GMT Message-Id: <20071119003737.21FDF2C039@rampart.timecastle.net> Mr. Christian Tismer, Thank you for your talk proposal submission. Please feel free to assign co-authors, attach files and add comments. Special requirements needed for your proposal (wired lan connection, white board, etc.) should be noted in a proposal comment. Wireless access, a microphone and a projector are standard equipment. Proposal reviewers will use the comment section to communicate with proposal authors and resolve any issues. Your e-mail address is never given out, even to reviewers. =============================================================================== 88. Stackless PyPy =============================================================================== :URL: http://us.pycon.org/2008/conference/proposals/88/ :Primary Author: Mr. Christian Tismer :Duration: 30 :Level: Advanced :Categories: concurrency, coroutines, implementations, pypy Summary ------- Stackless Python has been re-implemented for PyPy. This resulted in new insights about a not-so-new idea. The talk will give a higher level view of the underlying concepts of various Stackless implementations. Native CPython Stackless, Stackless emulation on top of PyPy using Greenlets, and Stackless built into PyPy compiled to C. Some emphasis is given to new underlying concepts like basic coroutines and composability. The known Stackless implementation turns out to be a special case of a general approach. Some knowledge about parallel programming is required, as provided by my Stackless 101 talk. Description ----------- This is a talk about the current development that takes place for Stackless Python. Parts of it are right now implemented for PyPy only, other things have been back-ported. the talk wants to give an overview of current status, future directions, and how PyPy has influenced and changed Stackless Python. There has been a related Pycon 2007 tak, which was hard to understand. Then there was a EuroPython talk with some improvements, but still not pleasant enough. On PyconUK 2007, I had a first success to show the new concepts in a broadly understandable way. This is now a minor issue, and the emphasis of the talk will no longer be the composability principle, since it is now really understood by myself. It will reduce to a smaller topic. Besides the fact that I always change my mind more or less, we will most probably talk about composability, see a couple of examples how different concepts work together, get some general picture of the Stackless implementation in PyPy, and see some first results about back-porting Stackless PyPy to CPython. There will also be some Python 3000 related stuff. It is also quite possible that we will talk about CSP, which is likely to become a major target of Stackless Python during the next months. I am not going to give a detailed talk layout, since everything is still in development and subject to change. But I can promise an interesting and entertaining session! There is one constraint: I can only give this talk if my Stackless Python 101 talk is accepted as well. Please make sure that these occur at least one day apart. -- The PyCon 2008 Program Committee -------------------------------------------------------------------------------- You have received this e-mail because you are participating in PyCon 2008. If you feel you have received this e-mail in error, please contact: Jeff Rush at jeff@taupro.com NOTE: This e-mail was generated automatically. Please do not reply to this message. ]