[pypy-svn] r44995 - in pypy/extradoc/talk/ep2007: . demo howtoeu interpreter pypy_10_and_jit pytest rpython
antocuni at codespeak.net
antocuni at codespeak.net
Fri Jul 13 09:32:00 CEST 2007
Author: antocuni
Date: Fri Jul 13 09:31:55 2007
New Revision: 44995
Modified:
pypy/extradoc/talk/ep2007/demo/ (props changed)
pypy/extradoc/talk/ep2007/demo/pickledtasklet.py (props changed)
pypy/extradoc/talk/ep2007/howtoeu/ (props changed)
pypy/extradoc/talk/ep2007/howtoeu/howtoeu.txt (contents, props changed)
pypy/extradoc/talk/ep2007/interpreter/ (props changed)
pypy/extradoc/talk/ep2007/interpreter/interpreter.txt (props changed)
pypy/extradoc/talk/ep2007/openspace_discussions.txt (contents, props changed)
pypy/extradoc/talk/ep2007/pypy_10_and_jit/ (props changed)
pypy/extradoc/talk/ep2007/pypy_10_and_jit/talk.txt (props changed)
pypy/extradoc/talk/ep2007/pytest/ (props changed)
pypy/extradoc/talk/ep2007/pytest/pytest.txt (props changed)
pypy/extradoc/talk/ep2007/rpython/ (props changed)
pypy/extradoc/talk/ep2007/stackless-essentials.txt (contents, props changed)
Log:
fixeol
Modified: pypy/extradoc/talk/ep2007/howtoeu/howtoeu.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/howtoeu/howtoeu.txt (original)
+++ pypy/extradoc/talk/ep2007/howtoeu/howtoeu.txt Fri Jul 13 09:31:55 2007
@@ -1,219 +1,219 @@
-
-.. include:: <s5defs.txt>
-
-
-==================================================
-How to do an open source EU research project
-==================================================
-
-
-:authors: Lene Wagner, Holger Krekel (merlinux GmbH)
-:event: 10.7.2007, EuroPython 2007, Vilnius
-
-
-Intro
-===================
-
-- we have participated in the PyPy project
-- both on technical and management levels
-- founded merlinux GmbH in 2004, doing various projects
-- we discuss *open source* research projects
-- skip "Intellectucal Property" issues
-
-EU Framework Research Programme
-====================================
-
-- IST = Information Society and Technology
-- PyPy was a STREP
-- FP7 spends some 20.000.000.000 Euro in 7 years
-- regularly publishes Work Programmes and Topics
-- puts out CALLS for Proposals
-- we mainly discuss FP7 (only few changes from FP6)
-
-Getting started
-=====================
-
-- visions / ideas?
-- reading Work programmes / CALL topics
-- finding people to collaborate
-- finding a set of organisations
-- drafting a proposal ...
-
-(Research) Objectives?
-==============================
-
-- formulate core research objective(s)
- (state of the art & how the project aims beyond)
-- formulate core technical objectives?
-- core other objectives? (methodological/social)
-
-can you summarize it on one page?
-
-The Proposal
-===============
-
-- High level Objectives
-- Impact on industry and society
-- management structures
-- work plan in long form
-- detailed description of work packages
-- Project duration, budget?
-
-Work Packages
-===================
-
-- each has a specific objective
-- Person Months allocated from Partners
-- Lead Partner
-- Deliverables (Reports, Releases, Papers)
-
-Consortium
-============================
-
-- looking for interested parties
-- consortium consists of organisations
-- is collective entity towards EU
-- requires co-ordinator/contact person for EU
-- receives and distributes money
-
-
-Applying to the EU
-=========================
-
-- answer to CALLS within stated deadline
-- co-ordinator registers project and proposal
-- proposals gets reviewed by *independent* experts
-- proposals receive points (PyPy had 26 out of 30)
-- Invitation to "negotiation"
-
-Negotiation
-==============
-
-- discuss criticism of reviewers, change proposal
-- Prepare paperwork (CPF = Contract Preparation Forms)
-- sign CONTRACT with the European Union
-
-Funding Schemes
-=====================
-
-- Universities receive (basically) 75% funding
-- Small/Medium Companies (SME) receive 75% funding of costs
-- actual or 20% flat administrative overheads accountable
-
-Signing the contract?
-========================
-
-signature of the (negotiated) contract:
-
-- is legally binding for all contractors and the EU
-- afterwards the EU does pre-payments (40-80%)
-- the consortium can ask for amendments later
-
-Infrastructure
-==================
-- ensure close collaboration of non co-located developers
-- ensure openness for external contributors
-- ensure consistency of codebase/project
-- PyPy: IRC, svn, mailing lists
-
-
-Management structures
-============================
-
-- Administrative team (preparing Consortium decisions)
-- Technical Board (discussing problems, deciding roadmap)
-- developer body (everybody can participate)
-- Consortium and Co-ordinator
-
-
-Meetings and Sprints
-============================
-
-- sprints provide the rhythm of the project
-- plan for core for newcomer-friendly sprints
-- integrate a model for funding new contributors!
-
-
-Contractual and actual developments
-=====================================
-- Contract implies a 'plan' for the development
-- Project may evolve into other directions
-- do checkpoints for assessing the work package status
-
-Planning for changes
-===========================
-
-- be able to shift work among partners
-- if necessary: amend work plan, change the contract with the EU
-- but: don't touch the objectives!
-
-
-Reporting / Deliverables
-============================
-
-- interim reviews each 12-18 months
-- Deliverables are: Reports, Releases etc.
-- Deadlines
-- official submission of Reports/Documentation to EU
-
-Recommendations
-====================
-
-- sprint-driven model of development;
-- share some funding with upcoming contributors;
-- balance contractual with community interests
-- consider changes to the contractual work plan if
- it fits the objectives better;
-
-More Recommendations
-========================
-- transparent and flat communication and decision culture
-- be ready to adjust roles and not stick to formal issues too much.
-- dual-use Deliverables for Community/Industry and EU contract purposes
-
-
-Roles and Responsbilities
-============================
-
-- assign responsibilities to people
-
- - per aspect (administration, technical, research)
- - per work package
-
-- plan for changing responsibilities
-
-Changes from FP6 to FP7
-=============================
-
-- apparently FP7 improves some regulations that PyPy found burdonsome
-- less collective financial responsibility
-- 75% funding for (small/medium) companies
-- subcontracting relaxed (important for international companies)
-
-
-What Remains?
-================================
-
-- build the project on a shared vision and shared interest
-- don't build it on money (too much)
-- get into contact with national support offices!
-- use the national and EU help infrastructure!
-
-
-Further information
-==========================
-
-- official EU FP7 website:
- http://cordis.europa.eu/fp7/home_en.html
-
-- information leaflet on FP7:
- http://ec.europa.eu/research/fp7/pdf/fp7-inbrief_en.pdf
-
-- Information and Communication Technology department:
- http://cordis.europa.eu/fp7/ict/
-
-- PyPy project http://pypy.org
-
-
-
-
+
+.. include:: <s5defs.txt>
+
+
+==================================================
+How to do an open source EU research project
+==================================================
+
+
+:authors: Lene Wagner, Holger Krekel (merlinux GmbH)
+:event: 10.7.2007, EuroPython 2007, Vilnius
+
+
+Intro
+===================
+
+- we have participated in the PyPy project
+- both on technical and management levels
+- founded merlinux GmbH in 2004, doing various projects
+- we discuss *open source* research projects
+- skip "Intellectucal Property" issues
+
+EU Framework Research Programme
+====================================
+
+- IST = Information Society and Technology
+- PyPy was a STREP
+- FP7 spends some 20.000.000.000 Euro in 7 years
+- regularly publishes Work Programmes and Topics
+- puts out CALLS for Proposals
+- we mainly discuss FP7 (only few changes from FP6)
+
+Getting started
+=====================
+
+- visions / ideas?
+- reading Work programmes / CALL topics
+- finding people to collaborate
+- finding a set of organisations
+- drafting a proposal ...
+
+(Research) Objectives?
+==============================
+
+- formulate core research objective(s)
+ (state of the art & how the project aims beyond)
+- formulate core technical objectives?
+- core other objectives? (methodological/social)
+
+can you summarize it on one page?
+
+The Proposal
+===============
+
+- High level Objectives
+- Impact on industry and society
+- management structures
+- work plan in long form
+- detailed description of work packages
+- Project duration, budget?
+
+Work Packages
+===================
+
+- each has a specific objective
+- Person Months allocated from Partners
+- Lead Partner
+- Deliverables (Reports, Releases, Papers)
+
+Consortium
+============================
+
+- looking for interested parties
+- consortium consists of organisations
+- is collective entity towards EU
+- requires co-ordinator/contact person for EU
+- receives and distributes money
+
+
+Applying to the EU
+=========================
+
+- answer to CALLS within stated deadline
+- co-ordinator registers project and proposal
+- proposals gets reviewed by *independent* experts
+- proposals receive points (PyPy had 26 out of 30)
+- Invitation to "negotiation"
+
+Negotiation
+==============
+
+- discuss criticism of reviewers, change proposal
+- Prepare paperwork (CPF = Contract Preparation Forms)
+- sign CONTRACT with the European Union
+
+Funding Schemes
+=====================
+
+- Universities receive (basically) 75% funding
+- Small/Medium Companies (SME) receive 75% funding of costs
+- actual or 20% flat administrative overheads accountable
+
+Signing the contract?
+========================
+
+signature of the (negotiated) contract:
+
+- is legally binding for all contractors and the EU
+- afterwards the EU does pre-payments (40-80%)
+- the consortium can ask for amendments later
+
+Infrastructure
+==================
+- ensure close collaboration of non co-located developers
+- ensure openness for external contributors
+- ensure consistency of codebase/project
+- PyPy: IRC, svn, mailing lists
+
+
+Management structures
+============================
+
+- Administrative team (preparing Consortium decisions)
+- Technical Board (discussing problems, deciding roadmap)
+- developer body (everybody can participate)
+- Consortium and Co-ordinator
+
+
+Meetings and Sprints
+============================
+
+- sprints provide the rhythm of the project
+- plan for core for newcomer-friendly sprints
+- integrate a model for funding new contributors!
+
+
+Contractual and actual developments
+=====================================
+- Contract implies a 'plan' for the development
+- Project may evolve into other directions
+- do checkpoints for assessing the work package status
+
+Planning for changes
+===========================
+
+- be able to shift work among partners
+- if necessary: amend work plan, change the contract with the EU
+- but: don't touch the objectives!
+
+
+Reporting / Deliverables
+============================
+
+- interim reviews each 12-18 months
+- Deliverables are: Reports, Releases etc.
+- Deadlines
+- official submission of Reports/Documentation to EU
+
+Recommendations
+====================
+
+- sprint-driven model of development;
+- share some funding with upcoming contributors;
+- balance contractual with community interests
+- consider changes to the contractual work plan if
+ it fits the objectives better;
+
+More Recommendations
+========================
+- transparent and flat communication and decision culture
+- be ready to adjust roles and not stick to formal issues too much.
+- dual-use Deliverables for Community/Industry and EU contract purposes
+
+
+Roles and Responsbilities
+============================
+
+- assign responsibilities to people
+
+ - per aspect (administration, technical, research)
+ - per work package
+
+- plan for changing responsibilities
+
+Changes from FP6 to FP7
+=============================
+
+- apparently FP7 improves some regulations that PyPy found burdonsome
+- less collective financial responsibility
+- 75% funding for (small/medium) companies
+- subcontracting relaxed (important for international companies)
+
+
+What Remains?
+================================
+
+- build the project on a shared vision and shared interest
+- don't build it on money (too much)
+- get into contact with national support offices!
+- use the national and EU help infrastructure!
+
+
+Further information
+==========================
+
+- official EU FP7 website:
+ http://cordis.europa.eu/fp7/home_en.html
+
+- information leaflet on FP7:
+ http://ec.europa.eu/research/fp7/pdf/fp7-inbrief_en.pdf
+
+- Information and Communication Technology department:
+ http://cordis.europa.eu/fp7/ict/
+
+- PyPy project http://pypy.org
+
+
+
+
Modified: pypy/extradoc/talk/ep2007/openspace_discussions.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/openspace_discussions.txt (original)
+++ pypy/extradoc/talk/ep2007/openspace_discussions.txt Fri Jul 13 09:31:55 2007
@@ -1,108 +1,108 @@
-
-What do you want PyPy to do?
-Open Space session at EP2007 2007-07-11
-================================================
-Purpose:
-- collect information about needs from PyPy and
- would-be PyPy users
-- answers from PyPy developers when/where applicable
-
-How was it done:
-- everyone present wrote their primary question
- and/or interest on a post-it
-- these were grouped to identify overlapping areas
- interest, largest areas were adressed first
-- a summary of the questions/interests grouped per
- area can be found below and the "answers" discussed
-
-Areas of questions/interests:
-
-RPython: stand alone and/or interfacing external libraries
---------------------------------------------------------------
-Questions/interests:
-- using RPython in CPython (unless PyPy can run all my Python
- 2 code next month)
-- how many are interested in RPython (in CPython, support
- available, stability)
-- RPython for Python extensions
-- external library interfacing (extension modules)
-- 3D graphics: Fast floating points? Fast math?
-
-Answers/comments:
-- CPython API support in PyPy is slow
-- RPython not complete yet (ex. ref counting)
-- The state of RCtypes (support it, refactor and change
- direction, future at all) is unclear - needs discussions
- (how - to use ctypes at (PyPy) application level?)
-- we need strategic discussions regarding how to interface
- with external clibraries, to be discussed during sprint
-- general need for refactoring - timespan will be roughly
- a year to have a PyPy that usable (while still not covering
- all extension modules)
-- for stand alone RPython applications there is need for usability
- fixes (shared interest) and speed/IO extensions
- (app-level solution)
-- regarding the question on 3D graphics (fast floating points, fast
- math) the answer is that it is fairly easy to add this and there is
- a matching interest in the PyPy dev-team in this area.
- The need to display/visualize is then a matter of general C extension
- interfacing
-
-Suggestions:
-- RCtypes: let´s experiment here and discuss approaches during the sprint
-
-Javascript backend/related areas
--------------------------------------
-Questions:
-- I want to write a parser in Python and port it to javascript
-- usable javascript backend
-- emulate pygame on flash player
-
-Answers/comments:
-- a parser is doable but you will encounter bugs, report them
- and they will be fixed - there is a matching interest here
- in the PyPy dev-team
-- there is also a document on http://codespeak.net/pypyXXX
- regarding parser creation
-- regarding emulating PyGame on a flahs player - this is doable
- but work needed, some rough estimates discussed were between
- 2-4 months because it´s connected to tweaking a backend or
- creating a new backend (which is an area we know a lot about;-)
- So doable, requires work and we are not too sure about the results ;-)
-
-Refactoring/usability
---------------------------------
-Questions:
-- how pypy goes about maintaining parts?
-- SLES/Solaris package? Light production usage?
-- be less hackish to use?
-- pypy 1.1.0 planning, which cleanups are we to tackle
- and who?
-- fixing/improving stackless, pickling and OO-support
-
-Answers/comments:
-- this was not discussed in particular due to time constraints
-- was also not prioritized because it contained several PyPy
- developers interests and we prioritized to try to answer
- "users/would-be "users" interests
-- it was apparent though during the entire discussion that
- we where discussing answers in the form of "doable" and
- "refactoring needed" which is what this area is all about
-
-Suggestions:
-- general refactoring/technical direction discussion in
- connection to the sprint
-
-
-Other areas of interests/questions
--------------------------------------
-Questions:
-- reducing the memory footprint of the Python interpreter
- (I want to run preferable several, securely separated interpreters
- on a resource constrained system (a phone specifically)
-- different language interpreters/front-ends
-
-Answers/comments:
-- these were not discussed due to time constraints
-- they will be taken into account when discussing general
- refactoring/technical direction
+
+What do you want PyPy to do?
+Open Space session at EP2007 2007-07-11
+================================================
+Purpose:
+- collect information about needs from PyPy and
+ would-be PyPy users
+- answers from PyPy developers when/where applicable
+
+How was it done:
+- everyone present wrote their primary question
+ and/or interest on a post-it
+- these were grouped to identify overlapping areas
+ interest, largest areas were adressed first
+- a summary of the questions/interests grouped per
+ area can be found below and the "answers" discussed
+
+Areas of questions/interests:
+
+RPython: stand alone and/or interfacing external libraries
+--------------------------------------------------------------
+Questions/interests:
+- using RPython in CPython (unless PyPy can run all my Python
+ 2 code next month)
+- how many are interested in RPython (in CPython, support
+ available, stability)
+- RPython for Python extensions
+- external library interfacing (extension modules)
+- 3D graphics: Fast floating points? Fast math?
+
+Answers/comments:
+- CPython API support in PyPy is slow
+- RPython not complete yet (ex. ref counting)
+- The state of RCtypes (support it, refactor and change
+ direction, future at all) is unclear - needs discussions
+ (how - to use ctypes at (PyPy) application level?)
+- we need strategic discussions regarding how to interface
+ with external clibraries, to be discussed during sprint
+- general need for refactoring - timespan will be roughly
+ a year to have a PyPy that usable (while still not covering
+ all extension modules)
+- for stand alone RPython applications there is need for usability
+ fixes (shared interest) and speed/IO extensions
+ (app-level solution)
+- regarding the question on 3D graphics (fast floating points, fast
+ math) the answer is that it is fairly easy to add this and there is
+ a matching interest in the PyPy dev-team in this area.
+ The need to display/visualize is then a matter of general C extension
+ interfacing
+
+Suggestions:
+- RCtypes: let´s experiment here and discuss approaches during the sprint
+
+Javascript backend/related areas
+-------------------------------------
+Questions:
+- I want to write a parser in Python and port it to javascript
+- usable javascript backend
+- emulate pygame on flash player
+
+Answers/comments:
+- a parser is doable but you will encounter bugs, report them
+ and they will be fixed - there is a matching interest here
+ in the PyPy dev-team
+- there is also a document on http://codespeak.net/pypyXXX
+ regarding parser creation
+- regarding emulating PyGame on a flahs player - this is doable
+ but work needed, some rough estimates discussed were between
+ 2-4 months because it´s connected to tweaking a backend or
+ creating a new backend (which is an area we know a lot about;-)
+ So doable, requires work and we are not too sure about the results ;-)
+
+Refactoring/usability
+--------------------------------
+Questions:
+- how pypy goes about maintaining parts?
+- SLES/Solaris package? Light production usage?
+- be less hackish to use?
+- pypy 1.1.0 planning, which cleanups are we to tackle
+ and who?
+- fixing/improving stackless, pickling and OO-support
+
+Answers/comments:
+- this was not discussed in particular due to time constraints
+- was also not prioritized because it contained several PyPy
+ developers interests and we prioritized to try to answer
+ "users/would-be "users" interests
+- it was apparent though during the entire discussion that
+ we where discussing answers in the form of "doable" and
+ "refactoring needed" which is what this area is all about
+
+Suggestions:
+- general refactoring/technical direction discussion in
+ connection to the sprint
+
+
+Other areas of interests/questions
+-------------------------------------
+Questions:
+- reducing the memory footprint of the Python interpreter
+ (I want to run preferable several, securely separated interpreters
+ on a resource constrained system (a phone specifically)
+- different language interpreters/front-ends
+
+Answers/comments:
+- these were not discussed due to time constraints
+- they will be taken into account when discussing general
+ refactoring/technical direction
Modified: pypy/extradoc/talk/ep2007/stackless-essentials.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/stackless-essentials.txt (original)
+++ pypy/extradoc/talk/ep2007/stackless-essentials.txt Fri Jul 13 09:31:55 2007
@@ -1,78 +1,78 @@
-Abstract ID: 62
-Abstract content:
-
-This is a re-worked, actualized and improved version of
-my talk at PyCon 2007. Repeating the abstract:
-
-As a surprise for people who think they know Stackless,
-we present the new Stackless implementation For PyPy,
-which has led to a significant amount of new insight
-about parallel programming and its possible implementations.
-We will isolate the known Stackless as a special case of
-a general concept.
-
-This is a Stackless, not a PyPy talk. But the insights presented
-here would not exist without PyPy's existance.
-
-Summary:
-
-Stackless has been around for a long time now. After several
-versions with different goals in mind, the basic concepts of
-channels and tasklets turned out to be useful abstractions,
-and since many versions, Stackless is only ported from version
-to version, without fundamental changes to the principles.
-
-As some spin-off, Armin Rigo invented Greenlets at a Stackless
-sprint. They are some kind of coroutines and a bit of special
-semantics. The major benefit is that Greenlets can run on
-unmodified CPython.
-
-In parallel to that, the PyPy project is in its fourth year
-now, and one of its goals was Stackless integration as an option.
-And of course, Stackless has been integrated into PyPy in a very
-nice and elegant way, much nicer than expected. During the design
-of the Stackless extension to PyPy, it turned out, that tasklets,
-greenlets and coroutines are not that different in principle,
-and it was possible to base all known parallel paradigms on
-one simple coroutine layout, which is as minimalistic as possible.
-
-It is a side effect of PyPy's simplicity, that even led to a
-pretty new concept for Stackless, that allows all the different
-switching paradigms to co-exist without interference. Users
-could go further and implement their own concurrency model,
-and it would neither interfere with others nor cost performance.
-
-Today's Stackless can be seen as a special case of the more general
-implementation given for PyPy. This implementation can also be taken
-as a reference about how Stackless is meant to be implemented.
-This reference implementation is completely written in Python.
-
-The talk will try to isolate the crucial design decisions in
-Stackless from implementation details. The reduced concepts
-are together the essentials of Stackless.
-
-Special emphasis is given to interactive examples, simple use-cases,
-and an animation that visually explains the new concept of
-composability.
-
-Primary authors: TISMER, Christian (tismerysoft GmbH)
-Co-Authors: -- none --
-Presenters: TISMER, Christian
-Track classification: Python Language and Libraries
-Submitted by: TISMER, Christian
-Submitted on: 25 May 2007 23:56
-Last modified on: 25 May 2007 23:56
-Status: SUBMITTED
-Comments :
-
-
-As this is a re-worked version of my PyCon 2007 talk, I would like
-to improve it by giving more examples, including some of
-Andrew Dahlke's PyCon talk.
-The original was quite short in explaining concepts, and moving
-over to the new concept of composability, quickly.
-I would lke to give more space to introducing the basic
-concepts this time, having more visualisation, iteractive sessions,
-and short repetitions and summaries.
-This talk intends to give some insight both to the novice and also
+Abstract ID: 62
+Abstract content:
+
+This is a re-worked, actualized and improved version of
+my talk at PyCon 2007. Repeating the abstract:
+
+As a surprise for people who think they know Stackless,
+we present the new Stackless implementation For PyPy,
+which has led to a significant amount of new insight
+about parallel programming and its possible implementations.
+We will isolate the known Stackless as a special case of
+a general concept.
+
+This is a Stackless, not a PyPy talk. But the insights presented
+here would not exist without PyPy's existance.
+
+Summary:
+
+Stackless has been around for a long time now. After several
+versions with different goals in mind, the basic concepts of
+channels and tasklets turned out to be useful abstractions,
+and since many versions, Stackless is only ported from version
+to version, without fundamental changes to the principles.
+
+As some spin-off, Armin Rigo invented Greenlets at a Stackless
+sprint. They are some kind of coroutines and a bit of special
+semantics. The major benefit is that Greenlets can run on
+unmodified CPython.
+
+In parallel to that, the PyPy project is in its fourth year
+now, and one of its goals was Stackless integration as an option.
+And of course, Stackless has been integrated into PyPy in a very
+nice and elegant way, much nicer than expected. During the design
+of the Stackless extension to PyPy, it turned out, that tasklets,
+greenlets and coroutines are not that different in principle,
+and it was possible to base all known parallel paradigms on
+one simple coroutine layout, which is as minimalistic as possible.
+
+It is a side effect of PyPy's simplicity, that even led to a
+pretty new concept for Stackless, that allows all the different
+switching paradigms to co-exist without interference. Users
+could go further and implement their own concurrency model,
+and it would neither interfere with others nor cost performance.
+
+Today's Stackless can be seen as a special case of the more general
+implementation given for PyPy. This implementation can also be taken
+as a reference about how Stackless is meant to be implemented.
+This reference implementation is completely written in Python.
+
+The talk will try to isolate the crucial design decisions in
+Stackless from implementation details. The reduced concepts
+are together the essentials of Stackless.
+
+Special emphasis is given to interactive examples, simple use-cases,
+and an animation that visually explains the new concept of
+composability.
+
+Primary authors: TISMER, Christian (tismerysoft GmbH)
+Co-Authors: -- none --
+Presenters: TISMER, Christian
+Track classification: Python Language and Libraries
+Submitted by: TISMER, Christian
+Submitted on: 25 May 2007 23:56
+Last modified on: 25 May 2007 23:56
+Status: SUBMITTED
+Comments :
+
+
+As this is a re-worked version of my PyCon 2007 talk, I would like
+to improve it by giving more examples, including some of
+Andrew Dahlke's PyCon talk.
+The original was quite short in explaining concepts, and moving
+over to the new concept of composability, quickly.
+I would lke to give more space to introducing the basic
+concepts this time, having more visualisation, iteractive sessions,
+and short repetitions and summaries.
+This talk intends to give some insight both to the novice and also
to experienced stackless users.
\ No newline at end of file
More information about the Pypy-commit
mailing list