[pypy-svn] r64371 - pypy/trunk/pypy/doc
cfbolz at codespeak.net
cfbolz at codespeak.net
Sun Apr 19 15:53:40 CEST 2009
Date: Sun Apr 19 15:53:39 2009
New Revision: 64371
towards a version of the release announcement
--- pypy/trunk/pypy/doc/release-1.1.0.txt (original)
+++ pypy/trunk/pypy/doc/release-1.1.0.txt Sun Apr 19 15:53:39 2009
@@ -1,63 +1,95 @@
-what we removed
+PyPy 1.1: Compatibility & Consolidation
- - JIT
+Welcome to the PyPy 1.1 release – the first release after the end of EU
+funding. This release focuses on making PyPy's Python interpreter more
+compatible with CPython (we are currently targetting CPython 2.5).
- - LLVM backend
- - JS backend
+Highlights of This Release
- - Aspect oriented programming
+.. Improvements to the Python Interpreter
- - Logic objspace
+ - More of CPython's standard-library extension modules are supported,
+ among them ctypes, sqlite3, csv. Most of these modules extension are
+ fully supported under Windows as well.
- - CPython extension compiler
-what we added
- - 2.5.2
- - ctypes
- - more modules: pysqlite & co.
- - new garbage collectors: moving GCs, e.g. generational, hybrid, etc., threads+gc work
- - memory wise optimizations (check it): mark-compact GC, shared instance
- dictionaries also for instances of old-style classes; user class instances
- often 50% of CPython size!
- performance improvements: between 0.8-2x (and in some corner case 3-4x)
- the time spent by CPython
- - pypy-jvm
- - improved pypy-cli clr module
- - compilation to maemo
- - reflective objspace (???)
+ the time spent by CPython XXX we should measure 1.0 and compare
+ - new garbage collectors: moving GCs, e.g. generational, hybrid, etc., threads+gc work
- - mention new jit developments, even if they are not included (???)
+ - Our Python interpreter now supports distutils as well as
+ easy_install for pure-Python modules.
- - check more what we did in the cleanup sprint
+ - We have tested PyPy with a number of third-party libraries. PyPy can
+ run now: Django, Pylons, BitTorrent, Twisted, SymPy, Pyglet, Nevow,
- - testing infrastructure
- - classic classes are by default now
+ - A buildbot was set up to run the various tests that PyPy is using
+ nightly on Windows and Linux machines:
- - examples of external libraries/app we run: pyglet, django, pylons,
- bittorrent, nevow, pynax, twisted, sympy
- - more windows support
+ - Sandboxing support: It is possible to translate the Python
+ interpreter in a special way so that the result is fully sandboxed.
- - PyPy's stackless module more complete: we added channel preferences which
- change details of the scheduling semantics.
- - better profiling support for PyPy
- - sandboxing
+ - memory wise optimizations (check it): mark-compact GC, shared instance
+ dictionaries also for instances of old-style classes; user class instances
+ often 50% of CPython size!
- - easy_install/distutils support
+ - The ``clr`` module was greatly improved. This module is used to
+ interface with .NET libraries when translating the Python
+ interpreter to the CLR.
+ - Stackless improvements: PyPy's ``stackless`` module is now more
+ complete. We added channel preferences which change details of the
+ scheduling semantics. In addition, the pickling of tasklets has been
+ improved to work in more cases.
+ - Classic classes are enabled by default now. In addition, they have
+ been greatly optimized and debugged:
+ - PyPy's Python interpreter can be translated to Java bytecode now to
+ produce a pypy-jvm. At the moment there is no integration yet with
+ Java libraries, so this is not really useful yet.
+ - We added cross-compilation machinery to our translation toolchain to
+ make it possible to cross-compile our Python interpreter to Nokia's
+ Maemo platform:
+ - The support for the trace hook in the Python interpreter was
+ improved to be able to trace the execution of builtin functions and
+ methods. In addition we implemented the ``_lsprof`` module, which is
+ equivalent to CPython's ``cProfile`` module.
+ - A number of rarely used features of PyPy were removed since the last
+ release because they were unmaintained and/or buggy. Those are: The
+ LLVM and the JS backends, the aspect-oriented programming features,
+ the logic object space, the extension compiler and the first
+ incarnation of the JIT generator. The new JIT generator is in active
+ development, but not included in the release.
More information about the Pypy-commit