[pypy-svn] r16244 - pypy/extradoc/sprintinfo

hpk at codespeak.net hpk at codespeak.net
Tue Aug 23 11:19:17 CEST 2005

Author: hpk
Date: Tue Aug 23 11:19:16 2005
New Revision: 16244

update today's planning

Modified: pypy/extradoc/sprintinfo/heidelberg-planning.txt
--- pypy/extradoc/sprintinfo/heidelberg-planning.txt	(original)
+++ pypy/extradoc/sprintinfo/heidelberg-planning.txt	Tue Aug 23 11:19:16 2005
@@ -37,7 +37,7 @@
       to reflect the 0.7 situation 
     - update getting_started.txt to reflect the 0.7 release
       and include instruction on how to translate
-      - possibly streamline the tool chain
+      - possibly streamline the tool chain (for genc/llvm) 
       - do we have an easy-to-explain tool chain working for win32? 
     - maybe globally use "bytecode interpreter" instead of "plain interpreter"  
   - write 0.7.0 release announcement + README 
@@ -59,6 +59,8 @@
   - Finish GIL-based threading: backend support, fix bugs? (arigo, rxe)
+    adding backend support is in-progress
   - (Decide whether to try to implement other threading locking policies)
     (probably not at the moment, let's see)
@@ -66,18 +68,43 @@
   - Isolate refcounting in genc, and    (cfbolz, pedronis)
     have an option to enable and use Boehm instead
-2.4.1 Compliance  (arre, tismer)
+    in progress of adding GCPolicy that encapsulates refcounting
+    and is to be called  from all places that now hardcode refcounting.
+2.4.1 Compliance  (arre, tismer)::
   - Recategorize the tests in core/non-core ( = language compliancy)
+    41 current-core tests should not be in core, 
+    11 current-non-core tests should be in core 
+     5 are about threading (should be core?)
   - test_unicode, test_codecs (ale, jacob)
+    test_unicode has one remaining error involving 
+    eval(unicode) which means that compile(unicode) does not work
+    currently. (see issue in the tracker, ludovic will try to look
+    into this briefly) 
   - Fix/adjust/prioritize compliance test problems
+    done: fixed binascii problems. 
+  - (tismer) in-progress: speeding up compilation on the 
+    translated pypy version by doing an external cpython-invocation 
+    to produce the code object. 
   - Some other "non-core" tests revealing real bugs/problems?
+  - from wednesday morning on most of us should work 
+    on compliancy related issues 
+  - (holger) try to fix the problem that you have to be in 
+    2.4.1/test in order to successfully run tests 
+  - NOTE: pypy-dist/lib-python/failure_list.txt 
+    contains ongoing anaylsis/Status for compliancy tests!
   - Fix bugs, missing features (some cause compliance regressions) 
   - Work on making the compiler interp-level 
       st->ast mostly done, should go into the release (ludal, nik)
+        integrated with a runtime option
+        need to fix astcompiler 
       ast->bytecode is not going to be done for the release
       (kept at app-level)
@@ -89,30 +116,34 @@
       inputs that are a single string are considered docstrings
       (also single unicode strings are considered docstrings)
-* Built-in modules
+Built-in modules::
   - Do we still miss important os.* functionality?
   - errno (easy for now)
-  - Enable our own array/_sre when translating (try with the current
-      _sre and its interp-level parts, otherwise just use the app-level
-      one)
+  - Enable our own array/_sre when translating 
+    (try with the current _sre and its interp-level parts, 
+    otherwise just use the app-level
+    one) (nik) in progress (trying to get '_sre' to translate)
   - (Review builtin modules again to see if we missed something)
   - 'math' must be finished (math.log(<long object>))
-Fix/garden issues for the release in the tracker
+Fix/garden issues for the release in the tracker::
   - Go over the issues in the tracker: close, postpone or fix them as needed
     for the release
   - Review Hildes_to_Heidel.txt contents too
-LLVM backend
+LLVM backend::
   - Improvement work to stabilize and match genc
   - (Try to share code with genc?)
   - Complete SoC GC framework (cfbolz)
+    in-progress: two more nights or so. 
   - (Start to think how/what is still missing to leverage it for Phase 2) 
   - (related: isolating refcounting)

More information about the Pypy-commit mailing list