[pypy-svn] r63267 - pypy/extradoc/talk/pycon2009/status
fijal at codespeak.net
fijal at codespeak.net
Tue Mar 24 10:14:42 CET 2009
Author: fijal
Date: Tue Mar 24 10:14:40 2009
New Revision: 63267
Modified:
pypy/extradoc/talk/pycon2009/status/status.txt
Log:
update a bit slides
Modified: pypy/extradoc/talk/pycon2009/status/status.txt
==============================================================================
--- pypy/extradoc/talk/pycon2009/status/status.txt (original)
+++ pypy/extradoc/talk/pycon2009/status/status.txt Tue Mar 24 10:14:40 2009
@@ -1,15 +1,17 @@
================================
-PyPy Python Interpreter status
+PyPy's Python Interpreter status
================================
What this talk is about
=======================
-* a bit of motivation
+* A bit of motivation
-* tell what Python Interpreter can run today
+* What we can run on top of PyPy
-* what we are heading for with the 1.1 release
+* How fast is PyPy?
+
+* 1.1 release coming
* Questions and Answers
@@ -29,8 +31,7 @@
=======================
* One should never be forced to write anything in C
- for performance reasons (with some exceptions: embedded
- devices etc.)
+ for performance reasons (with some exceptions possibly)
* Just-in-time compiler should make number-crunching
and static-enough code fast enough
@@ -41,10 +42,15 @@
==========================
* first sprint 2003, about 30 more by now
+
* CPython/Psyco/Jython/Stackless developers participating
+
* MIT-License, more sprints
+
* EU Research project 2004-2007
-* 2007-2008 - open source project
+
+* 2007-now - open source project
+
* some google sponsoring
Getting Production ready
@@ -134,7 +140,6 @@
* http://twistedmatrix.com/
-
Other software
==============
@@ -151,7 +156,7 @@
* various smaller things, templating engines
Obscure details that people rely on
-===================================
+=======================================
* non-string keys in __dict__ of types
@@ -165,22 +170,13 @@
* refcounting details
-Transition to 2.5
-==========================
-
-* SOC project Bruno Gola
-
-* almost complete
-
-* missing more testing, stdlib porting
-
Conclusion on Compatibility
============================
* lessons learned: There is no feature obscure enough for people
not to rely on it.
-* pypy-c interpreter probably the most compatible to CPython
+* pypy-c interpreter probably the most compatible to CPython 2.5
* main blocker for running apps will be missing external modules
@@ -199,14 +195,14 @@
Speed - JIT generator
=====================
-* not ready yet!
+* 20-30x faster on small examples
-* will be super fast
+* nice proof of concept
-* some prototypes, research ongoing
+* a bit of time needed to speed up large python
+ programs
-* psyco is a nice proof that this approach
- would work
+* probably won't make it to 1.1
Memory - comparison with CPython
===================================
@@ -221,7 +217,6 @@
* GCs are semi-decent
-
Threading / Stackless
===================================
@@ -246,21 +241,6 @@
* contributors wanted!
-Sandboxing
-==========
-
-* fully sandboxed python interpreter
-
-* all external calls to C goes via another
- python process
-
-* special library for making custom
- policies
-
-.. image:: sandboxed.png
- :scale: 30
- :align: center
-
pypy-c on small devices
===============================
@@ -271,15 +251,21 @@
- share interpreter state across processes
- pypy approach a very good fit!
-1.1 release goals
+1.1 release
===================================
- compatible to Python 2.5.2
+
- well tested on win/linux 32 bit
+
- running major packages unmodified
+
- easy_install/distutils working
+
- help e.g. by writing ctypes modules
+- hopefully next month
+
Contact / Q&A
==========================
More information about the Pypy-commit
mailing list