[pypy-svn] r49799 - pypy/extradoc/planning/roadmap

xoraxax at codespeak.net xoraxax at codespeak.net
Fri Dec 14 18:38:31 CET 2007


Author: xoraxax
Date: Fri Dec 14 18:38:30 2007
New Revision: 49799

Modified:
   pypy/extradoc/planning/roadmap/cpython_replacement.txt
Log:
Add gtk and a small paragraph to separate module compilation.


Modified: pypy/extradoc/planning/roadmap/cpython_replacement.txt
==============================================================================
--- pypy/extradoc/planning/roadmap/cpython_replacement.txt	(original)
+++ pypy/extradoc/planning/roadmap/cpython_replacement.txt	Fri Dec 14 18:38:30 2007
@@ -23,6 +23,11 @@
 to recompile all of PyPy every time you want to integrate a new extension
 module. This requires supporting separate compilation.
 
+Also this would be interesting ground work for a try to compile cpython modules
+with a pypy-supplied Python.h file and link them to pypy. This would require
+writing a lot of new functions (for the CPython API), though. Also it is not
+clear how large the expected speed impact would be (because of e. g. pinning).
+
 Support a tool like Swig or Boost
 =================================
 
@@ -102,7 +107,8 @@
 
 One of the C extension modules that we need to have in order to get
 traction is support for one of the multi-platform GUI toolkits. The
-choice is probably between Qt and wxWindows, with Tkinter as a
+choice is probably between gtk (in use by olpc and others), Qt (written in c++,
+using SIP to get a cpython package) and wxWindows, with Tkinter as a
 possible third. Someone with more understanding of the Python
 community than us should make the pick. Which one would bring more
 users to PyPy? Would any one of them prompt proponents of other



More information about the Pypy-commit mailing list