Author: Maciej Fijalkowski <[email protected]> Branch: release-2.2.x Changeset: r68002:725bbfa926bd Date: 2013-11-13 10:15 +0200 http://bitbucket.org/pypy/pypy/changeset/725bbfa926bd/
Log: start light, reflow the paras diff --git a/pypy/doc/release-2.2.0.rst b/pypy/doc/release-2.2.0.rst --- a/pypy/doc/release-2.2.0.rst +++ b/pypy/doc/release-2.2.0.rst @@ -45,23 +45,27 @@ Highlights ========== -* Our Garbage Collector is now "incremental". It should avoid almost all pauses due - to a major collection taking place. Previously, it would pause the program (rarely) - to walk all live objects, which could take arbitrarily long if your process is using - a whole lot of RAM. Now the same work is done in steps. This should make PyPy - more responsive, e.g. in games. There are still other pauses, from the GC and the JIT, - but they should be on the order of 5 milliseconds each. +* Our Garbage Collector is now "incremental". It should avoid almost + all pauses due to a major collection taking place. Previously, it + would pause the program (rarely) to walk all live objects, which + could take arbitrarily long if your process is using a whole lot of + RAM. Now the same work is done in steps. This should make PyPy + more responsive, e.g. in games. There are still other pauses, from + the GC and the JIT, but they should be on the order of 5 + milliseconds each. -* The JIT counters for hot code were never reset, which meant that a process running - for long enough would eventually JIT-compile more and more rarely executed code. - Not only is it useless to compile such code, but as more compiled code means more - memory used, this gives the impression of a memory leak. This has been tentatively +* The JIT counters for hot code were never reset, which meant that a + process running for long enough would eventually JIT-compile more + and more rarely executed code. Not only is it useless to compile + such code, but as more compiled code means more memory used, this + gives the impression of a memory leak. This has been tentatively fixed by decreasing the counters from time to time. -* NumPy has been split: now PyPy only contains the core module, called ``_numpypy``. - The ``numpy`` module itself has been moved to ``https://bitbucket.org/pypy/numpy``. - You need to install it separately in a virtualenv with - ``pip install git+https://bitbucket.org/pypy/numpy.git``. +* NumPy has been split: now PyPy only contains the core module, called + ``_numpypy``. The ``numpy`` module itself has been moved to + ``https://bitbucket.org/pypy/numpy``. You need to install it + separately in a virtualenv with ``pip install + git+https://bitbucket.org/pypy/numpy.git``. * improvements to non-inlined calls @@ -71,17 +75,19 @@ * improvements in buffer copying -* tk is supported (XXX was already in pypy 2.1 it seems?? maybe not correctly packaged?) +* tk is supported (XXX was already in pypy 2.1 it seems?? maybe not + correctly packaged?) -* We finally wrote all the missing ``os.xxx()`` functions. There are a lot of strange - ones that nobody ever heard about, except those who really need them. +* We finally wrote all the missing ``os.xxx()`` functions. There are + a lot of strange ones that nobody ever heard about, except those who + really need them. * numpy C API - the core module is included in PyPy 2.2, but you must now install - an external fork of numpy from https://bitbucket.org/pypy/numpy + the core module is included in PyPy 2.2, but you must now install an + external fork of numpy from https://bitbucket.org/pypy/numpy -removed in favor of an external numpy fork -at https://bitbucket.org/pypy/numpy +removed in favor of an external numpy fork at +https://bitbucket.org/pypy/numpy _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
