[pypy-svn] r51064 - pypy/extradoc/talk/rupy2008

fijal at codespeak.net fijal at codespeak.net
Sat Jan 26 13:12:30 CET 2008


Author: fijal
Date: Sat Jan 26 13:12:30 2008
New Revision: 51064

Modified:
   pypy/extradoc/talk/rupy2008/abstract.txt
Log:
First approach to abstract.


Modified: pypy/extradoc/talk/rupy2008/abstract.txt
==============================================================================
--- pypy/extradoc/talk/rupy2008/abstract.txt	(original)
+++ pypy/extradoc/talk/rupy2008/abstract.txt	Sat Jan 26 13:12:30 2008
@@ -2,22 +2,13 @@
 
 Title: PyPy, Python interpreter written in Python
 
-Abstract: XXX
+Abstract: In this talk I would like to present the PyPy project, our motivation,
+state of art and targets. PyPy is both an extremely flexible python interpreter
+written in Python itself to avoid burden of writing in low-level languages
+(like C) and compiler toolchain which compiles restricted python to a variety
+of lower-level platforms (including C/POSIX, CLI, JVM...). I would like to
+present some cool features, especially those created since the last rupy
+conference in 2007. Also, I would like to showcase directions in which
+the PyPy project is going, including even more agressive JIT compilation.
 
-Why another python interpreter?
-
-CPython is cool, but has limitations.
-
-Writing in C is ugly and unefficient.
-
-Let's write high-level interpreter in high-level language!
-
-Our cool features (which you haven't seen yet):
-
-* sandboxing
-* jit (python is too dynamic, let's compile it dynamically)
-* stackless (?)
-* frame pickling
-* gc in action
-
-xxx
\ No newline at end of file
+Details about the PyPy project can be seen at http://codespeak.net/pypy/
\ No newline at end of file



More information about the Pypy-commit mailing list