[pypy-svn] r19227 - pypy/extradoc/talk/pycon2006

hpk at codespeak.net hpk at codespeak.net
Mon Oct 31 13:40:26 CET 2005


Author: hpk
Date: Mon Oct 31 13:40:24 2005
New Revision: 19227

Modified:
   pypy/extradoc/talk/pycon2006/pylib.txt
Log:
slightly restructured the pylib proposal 
and submitted it to Pycon 2006. 

note that the pycon submission structure 
does not match the structure we used 
in svn.  should have checked that earlier myself 
i guess ... 

basically one needs a summary with 250-1000 words
and a presentation outline really is supposed to 
be the full presentation. 



Modified: pypy/extradoc/talk/pycon2006/pylib.txt
==============================================================================
--- pypy/extradoc/talk/pycon2006/pylib.txt	(original)
+++ pypy/extradoc/talk/pycon2006/pylib.txt	Mon Oct 31 13:40:24 2005
@@ -21,45 +21,30 @@
 
 Title: using the py library (apart from py.test) 
 
-Already known for the widely used py.test tool, the
-"py lib" has more to offer.  We are going to explore the
-experimental package "name export mechanism" also involving
-lazy imports, a lightweight tag/keyword-based logging scheme, 
-subversion and local Path objects and compatibility modules that 
-make recent Python library modules uniformly available from older 
-Python versions.  We also will glance into the current state of 
-"py.execnet" which explores new interprocess-communication 
-facilities.  All of these features are already used by a growing 
-number of projects.  We will give interactive examples and 
-conclude with an outlook. 
-
-Presentation Outline
---------------------
-
 The py lib is a development support library and evolves itself
-from a strictly test-driven development process.  Apart from
-its intense usage in the PyPy project a number of other
-projects have adapted its methods.  We plan to give usage
-examples for various parts of the py library.  The current key
-parts of the py lib we will present are:
+from a strictly test-driven development process.  Already
+known for the widely used py.test tool, the "py lib" has more
+to offer.  
+
+Apart from its intense usage in the PyPy project a number of
+other projects have adapted its methods.  We plan to give
+usage examples for various parts of the py library: 
 
-- py.log: keyword/subscription based lazy logging 
-- py.compat: provides standard library modules for older python versions
+- py.log:     keyword/subscription based lazy logging 
+- py.compat:  provides standard library modules for older python versions
 - py.initpkg: export name/lazy import mechanism ("import py" 
               is all you ever need to do).
-- py.path.*: path objects unifying access to svn- and
-             local filesystems. 
+- py.path:    path objects unifying access to svn- and
+              local filesystems. 
 - py.execnet: ad-hoc distributing programs across ssh- and process
               barriers. 
 
-We'll conclude with some of the next challenges for py lib
-development: 
+All of these features are already used by a growing number of 
+projects.  We will give interactive examples and conclude 
+with an outlook. 
 
-- extending py.execnet to use it for peer-to-peer situations
-- extending/refactoring py.path to support in-memory 
-  and in general more filesystems 
-- integrating twisted testing functionality into py.test 
-- a release plan 
+Presentation Outline (optional)
+---------------------------------
 
 Intended audience
 -----------------



More information about the Pypy-commit mailing list