[pypy-svn] r80060 - pypy/extradoc/planning

[arigo at codespeak.net]

Author: arigo
Date: Tue Dec 14 18:34:39 2010
New Revision: 80060

Modified:
   pypy/extradoc/planning/1.4.1.txt
Log:
Updated and finalized the file, which is now looking less like planning
and more like a summary of the changes for a release announcement.


Modified: pypy/extradoc/planning/1.4.1.txt
==============================================================================
--- pypy/extradoc/planning/1.4.1.txt	(original)
+++ pypy/extradoc/planning/1.4.1.txt	Tue Dec 14 18:34:39 2010
@@ -2,6 +2,8 @@
 Differences between releases 1.4 and 1.4.1
 ==========================================
 
+Migrated to mercurial.
+
 
 * In long-running processes, the assembler generated by old JIT-compilations
   is now freed.  There should be no more leak, however long the process runs.
@@ -9,27 +11,24 @@
 * Improve the performance of the ``binascii`` module, and of ``hashlib.md5``
   and ``hashlib.sha``.
 
-* Fix two corner cases in the GC (one in minimark, one in asmgcc+JIT).
+* Fix argument processing (now e.g. ``pypy -OScpass`` works like
+  it does on CPython --- if you have a clue what it does there ``:-)`` )
 
 * Fix cpyext on Mac OS X.  (Loading C extension modules in PyPy is still
   considered *alpha stage!*)
 
+* Fix two corner cases in the GC (one in minimark, one in asmgcc+JIT).
+  This notably prevented "pypy translate.py -Ojit" from working on Windows,
+  leading to crashes.
+
 * Fixed a corner case in the JIT's optimizer, leading to "Fatal RPython
   error: AssertionError".
 
-* Added some missing functions from the 'os' module.
+* Added some missing built-in functions into the 'os' module.
 
 * Fix ctypes (it was not propagating keepalive information from c_void_p).
 
-
-Plan:
-
-* Out of line guards (?) -> after the release
-
-* Merge jit-unroll-loops (?) -> after the release
-
-* Migrate to mercurial -> should not be a blocker
-
-* Understand what's going on on Windows with pypy-c translate.py -Ojit
-
-* finish the removal of sys.setrecursionlimit()
+* Made sys.setrecursionlimit() a no-op that just prints a warning.
+  Instead, we rely purely on the built-in stack overflow detection mechanism,
+  which also gives you a RuntimeError -- just not at some exact recursion
+  level.