[pypy-svn] r3835 - pypy/trunk/doc/funding
hpk at codespeak.net
hpk at codespeak.net
Tue Apr 6 16:19:36 CEST 2004
Author: hpk
Date: Tue Apr 6 16:19:35 2004
New Revision: 3835
Modified:
pypy/trunk/doc/funding/B6.7.wp03_synchronisation.txt
pypy/trunk/doc/funding/B6.7.wp04_core.txt
pypy/trunk/doc/funding/B6.7.wp05_translation.txt
pypy/trunk/doc/funding/B6.7.wp08_dynamic_optimisation.txt
pypy/trunk/doc/funding/B6.7.wp12_validations.txt
pypy/trunk/doc/funding/changelog-wp.txt
Log:
we now explicitely rely stronger than before now on collaboration and
contribution from existing open source projects, specific communities
and developers.
The responses should be modified to reflect this change
and the "collaborate stronger, expect contributions and thus
take higher risks if the contribution don't happen as expected"
This adds a strong argument why we think we survive the budget cuts
without reducing too much in scope.
Modified: pypy/trunk/doc/funding/B6.7.wp03_synchronisation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp03_synchronisation.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp03_synchronisation.txt Tue Apr 6 16:19:35 2004
@@ -24,8 +24,8 @@
Keeping PyPy in sync with potential changes to Standard Python.
Support a subset of the CPython API for compatibility with
-extension modules.
-Facilitate porting of extension modules to PyPy.
+extension modules. Facilitate porting of extension modules to PyPy.
+Collaborate strongly with CPython developer communities.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
@@ -36,7 +36,7 @@
Monitor the development of Standard Python for its ongoing changes.
Check the relevance of the changes concerning the structure of
-PyPy.
+PyPy. Collaborate with CPython developer communities.
Embed the relevant changes with proper testing, notifying the other
concurrent tasks of these changes.
Investigate tools which could partially automate
@@ -45,7 +45,7 @@
**Task 2**
Investigate different solutions to address compatibility with
-existing C extensions.
+existing C extensions. Collaborate with CPython developer communities.
Support a subset of the CPython API. Facilitate porting of
more involved extensions.
Investigate adjusting existing interface generators (in particular SWIG, used e.g
Modified: pypy/trunk/doc/funding/B6.7.wp04_core.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp04_core.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp04_core.txt Tue Apr 6 16:19:35 2004
@@ -25,6 +25,7 @@
Building a complete Python interpreter written in Python,
using a subset of Python that avoids dynamic features
which would impair the objectives of WP05_ (RPython).
+Collaborate with CPython core developers.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
@@ -50,7 +51,8 @@
This task excludes the standard extension modules and the
parser and bytecode compiler, which for the purpose of
testing are borrowed from the underlying CPython interpreter
-on top of which our interpreter runs.
+on top of which our interpreter runs. Collaborate strongly
+with CPython core developers via the python-dev mailing list.
**Task 2**
@@ -73,10 +75,12 @@
**Task 3**
Complete the interpreter with a Python source parser and bytecode
-compiler.
+compiler. Collaborate with various core developers involved
+with new parsing and compiling techniques.
- Implement a Python parser and bytecode compiler in Python by
- leveraging existing research and implementation work.
+ leveraging existing research and implementation work. Reuse
+ code and ideas from ongoing open source projects.
- Design a flexible way to insert the compiler into the
code base, easing future experimentation with the syntax.
Modified: pypy/trunk/doc/funding/B6.7.wp05_translation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp05_translation.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp05_translation.txt Tue Apr 6 16:19:35 2004
@@ -25,7 +25,7 @@
Analysis and translation of the PyPy core (WP04_) into
efficient low-level code (C, Pyrex, Java, others).
Providing a Runtime Library for the translated versions
-of PyPy.
+of PyPy.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
@@ -57,7 +57,8 @@
code (with C being the primary target) and compiling it.
- Create a build process for statically generating and running
- a low-level PyPy interpreter and object space.
+ a low-level PyPy interpreter and object space. Collaborate
+ with LLVM (Low level virtual Machine) core developers.
- Provide hooks into internals to alter translation aspects.
@@ -71,11 +72,13 @@
However, certain aspects such as memory management and threading models
are to be implemented in a modular way.
-- Implement a minimal C-runtime for the translated PyPy
+- Implement a minimal C-runtime for the translated PyPy, strongly
+ collaborate with CPython core developers.
- Integrate Memory Management, threadings models, and other aspects in a
modular way into both the C-runtime and the statically generated PyPy low
- level code.
+ level code. Improve on existing memory management techniques and open
+ source projects.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
Modified: pypy/trunk/doc/funding/B6.7.wp08_dynamic_optimisation.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp08_dynamic_optimisation.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp08_dynamic_optimisation.txt Tue Apr 6 16:19:35 2004
@@ -54,7 +54,8 @@
Make the JIT compiler flexible and portable.
- Enable dynamic foreign function calls. Allow language users to
- use them in their applications.
+ use them in their applications. Collaborate strongly with
+ core developers from the CTypes and SWIG open source projects.
- Design and implement a back-end component for dynamically emitting
machine code for multiple processor architectures.
Modified: pypy/trunk/doc/funding/B6.7.wp12_validations.txt
==============================================================================
--- pypy/trunk/doc/funding/B6.7.wp12_validations.txt (original)
+++ pypy/trunk/doc/funding/B6.7.wp12_validations.txt Tue Apr 6 16:19:35 2004
@@ -47,8 +47,8 @@
Look up existing libraries. Typical libraries like the Zope Enterprise
Objects (ZEO) or CORBA/Java RMI models require programs to be aware of
the remote execution model; by contrast, experimentally build the support
-for an equivalent functionality directly into the language.
-Report on the novel future directions.
+for an equivalent functionality directly into the language. Collaborate
+with existing open source projects. Report on the novel future directions.
**Task 3**
@@ -57,7 +57,8 @@
Look up existing libraries. Persistence is never fully orthogonal without
advanced language support, as witnessed by libraries like the Zope Database
(ZODB); we will build an experimental object space that can provide full
-orthogonally. Report on the novel future directions.
+orthogonally. Collaborate with ZODB and PyPersyst developer communitiies.
+Report on the novel future directions.
.. include:: wp-tableend.asc
.. include:: wp-tablebegin.asc
Modified: pypy/trunk/doc/funding/changelog-wp.txt
==============================================================================
--- pypy/trunk/doc/funding/changelog-wp.txt (original)
+++ pypy/trunk/doc/funding/changelog-wp.txt Tue Apr 6 16:19:35 2004
@@ -31,16 +31,19 @@
WP03 -33% budget, added 1 report deliverable::
more dissemination, more detailed descriptions of pre-existing tasks, focused on
- synchronization possibilities with CPython
+ synchronization possibilities with CPython, collaborate stronger with
+ developer communities
WP04 -33% budget, added 1 report deliverable::
tracing B6/B1, rearranged resource allocation (PBF), select/specify
language compliancy and focus on providing a "Research tool", more
- explicit dissemination also to non-python communities
+ explicit dissemination also to non-python communities, collaborate
+ stronger with developer communities
WP05 -33% budget, added 2 publication deliverables::
tracing B1/B6, rearranged resource allocation (PBF), much more
- detailed tasks, more explicit dissemination also to non-python communities
+ detailed tasks, more explicit dissemination also to non-python communities,
+ collaborate with other open source projects where appropriate
WP06 -50% budget, added 1 integration deliverable::
tracing B1/B6, rearranged resource allocation (MPI), much more
@@ -56,7 +59,8 @@
WP08 -30% budget, split first deliverables into two, added 2 publication deliverables::
tracing B1/B6, rearranged resource allocation (PBF), more detailed
tasks, more explicit dissemination also to non-python communities, emphasize
- measurable half-speed of C for algorithmic code,
+ measurable half-speed of C for algorithmic code, collaborate
+ with specific open source projects
WP09 -0% budget, added 1 assessment deliverable::
tracing B1/B6, more detailed description of tasks
More information about the Pypy-commit
mailing list