[pypy-svn] r12508 - pypy/dist/pypy/documentation
hpk at codespeak.net
hpk at codespeak.net
Thu May 19 12:56:35 CEST 2005
Author: hpk
Date: Thu May 19 12:56:35 2005
New Revision: 12508
Modified:
pypy/dist/pypy/documentation/release-0.6.txt
Log:
issue16 in-progress
refactoring, streamlining and slightly-reformatting
the release announcement. One open question is how
to present the core team/contributors and organizations.
Do we want to append all names at the end or just
put a link to some page listing all of them?
Modified: pypy/dist/pypy/documentation/release-0.6.txt
==============================================================================
--- pypy/dist/pypy/documentation/release-0.6.txt (original)
+++ pypy/dist/pypy/documentation/release-0.6.txt Thu May 19 12:56:35 2005
@@ -1,55 +1,58 @@
+The PyPy 0.6 release
+--------------------
+*The PyPy Development Team is happy to announce the first
+public release of PyPy after two years of spare-time and
+half a year of EU funded development. The 0.6 release
+is eminently a preview release.*
-*The PyPy Development Team is happy to announce the release 0.6 of PyPy
-interpreter and technology. This is the first public release and is
-eminently a preview release.*
-
-What is is, download and links
--------------------------------
-
-PyPy is a reimplementation of Python written in Python itself.
-
-The long term goals are an implementation that is flexible and easy to
-experiment with and retarget to different platforms (also non-C ones)
-and such that high performance can be achieved through high-level
-implementations of especially dynamic optimisation techniques.
+What it is and where to start
+-----------------------------
+
+ Getting started: http://codespeak.net/pypy/index.cgi?doc/getting_started.html
+
+ PyPy Documentation: http://codespeak.net/pypy/index.cgi?doc
+
+ PyPy Homepage: http://codespeak.net/pypy/
+
+PyPy is a MIT-licensed reimplementation of Python written in
+Python itself. The long term goals are an implementation that
+is flexible and easy to experiment with and retarget to
+different platforms (also non-C ones) and such that high
+performance can be achieved through high-level implementations
+of dynamic optimisation techniques.
The interpreter and object model implementations shipped with 0.6 can
be run on top of CPython and implement the core language features of
-Python as of CPython 2.3. They pass a substantial part (~90%) of
-CPython test-suite tests not depending on C extension modules. Some of
+Python as of CPython 2.3. PyPy passes around 90% of the Python language
+regression tests that do not depend deeply on C-extensions. Some of
that functionality is still made available by PyPy piggy-backing on
the host CPython interpreter. Double interpretation and abstractions
in the code-base make it so that PyPy running on CPython is quite slow
-(around 2000x slower than CPython ), this is to be expected.
+(around 2000x slower than CPython ), this is expected.
This release is intended for people that want to look and get a feel
into what we are doing, playing with interpreter and perusing the
codebase. Possibly to join in the fun and efforts.
-For download links and further information and documentation see
-(most of PyPy is realeased under the MIT license):
-
-- Download PyPy 0.6: http://xxx
-- Getting started: http://codespeak.net/pypy/index.cgi?doc/getting_started.html
-- PyPy Documentation: http://codespeak.net/pypy/index.cgi?doc
-- PyPy Homepage: http://codespeak.net/pypy/
-- PyPy 0.6 License: http://xxx
-
Interesting bits and highlights
---------------------------------
-The release is also a snap-shot of our ongoing efforts, interesting
-things and highlights included, related to the interpreter and beyond:
+The release is also a snap-shot of our ongoing efforts towards
+low-level translation and experimenting with unique features.
-* In PyPy bytecode interpretation and the implementation of objects
- semantics (as a library of objects) are separated, apart the
- standard implementation of those (what we call the standard object
- space) PyPy comes with experimental object spaces augmenting the
+* By default, PyPy is a Python version that works completely
+ with new-style-classes semantics. However, there is some support
+ for old-style classes through a custom metaclass.
+
+* In PyPy, bytecode interpretation and object manipulations
+ are well separated between a bytecode interpreter and an
+ object space which implements operations on objects.
+ PyPy comes with experimental object spaces augmenting the
standard one through delegation:
- an experimental object space that does extensive tracing of
- object operations;
+ bytecode and object operations;
- the 'thunk' object space that implements lazy values and a 'become'
operation that can exchange object identities.
@@ -58,43 +61,44 @@
PyPy*. (See demo/fibonacci.py and demo/sharedref.py for examples
about the 'thunk' object space.)
-* The core of PyPy only implements new-style classes, old-style
- classes are basically implemented, apart some hooks, as what is in
- principle user-level code (what we call app-level), and then
- integrated with rest (there's an interpreter option --old-style to
- make them the default metaclass).
-
-* PyPy is intended to be translated to low-level languages to regain
- speed, for that we have developed what we call the annotator, which
- is capable of reconstructing type information for our code-base,
- which is written respecting some restrictions, and similarly written
- code. The annotator right now is already capable of successfully
- type annotating basically *all* of PyPy code-base, and is included
- with 0.6.
+* The 0.6 release also contains a snapshot of our translation-efforts
+ to lower level languages. For that we have developed an
+ annotator which is capable of infering type information
+ across our code base. The annotator right now is already
+ capable of successfully type annotating basically *all* of
+ PyPy code-base, and is included with 0.6.
* From type annotated code low-level code needs to be generated,
backends for various targets (C, LLVM,...) are included, they are
all somehow incomplete and have been and are quite in flux. What is
shipped with 0.6 is able to deal with more or less small/medium examples.
-Getting started <http://codespeak.net/pypy/index.cgi?doc/getting_started.html> has more information about how to try out these features
-and tools.
-
Ongoing work and near term goals
---------------------------------
-Generating low-level target code is the main area we are working right
-now, our near term efforts aiming August/September of this year are
-focused on producing a stand-alone and low-level translated version of
-PyPy with speed much nearer to CPython range.
+Generating low-level code is the main area we are hammering on in the
+next months, our plan is to produce a PyPy version in August/September
+that does not need to be interpreted by CPython anymore and will
+thus run considerably faster than the 0.6 preview release.
+
+Please feel free to give feedback and raise questions. Here is
+how you can contact or join us:
+
+ http://codespeak.net/pypy/index.cgi?contact
+PyPy has been a community effort from the start and it would
+not have got that far without the coding and feedback support
+from numerous people. (XXX insert some link here?)
-The PyPy Development Team
+have fun,
-**xxx all contributor names in some order (?)**
+ the PyPy Development Team
+Disclaimer:
-PyPy development and activities happens as open source source project under the http://codespeak.net/ umbrella and through a consortium funded by a EU IST research grant:
+PyPy development and activities happens as open source source
+project under the http://codespeak.net/ umbrella and with
+the support of a consortium funded by a EU IST research grant:
**(xxx consortium partners?? )**
More information about the Pypy-commit
mailing list