[pypy-svn] rev 1824 - pypy/trunk/doc/funding
pedronis at codespeak.net
pedronis at codespeak.net
Sun Oct 12 22:21:10 CEST 2003
Author: pedronis
Date: Sun Oct 12 22:21:09 2003
New Revision: 1824
Modified:
pypy/trunk/doc/funding/B3.impact.txt (contents, props changed)
Log:
done some ReST formatting.
Modified: pypy/trunk/doc/funding/B3.impact.txt
==============================================================================
--- pypy/trunk/doc/funding/B3.impact.txt (original)
+++ pypy/trunk/doc/funding/B3.impact.txt Sun Oct 12 22:21:09 2003
@@ -82,16 +82,16 @@
project, and hope to see it going forward. The PyPy team includes
some of the best minds in the Python community.
-Unlike Perl or Tcl, Python is not a "one-implementation" language, and
-consequently the formal language specification should have priority
-over the behavior of a particular implementation. The PyPy project
-will reinforce this idea, and can be useful in sorting out ambiguities
-in the specification. It is even possible that PyPy will eventually
-serve as an "executable specification" for the language, and the
-behavior of one of PyPy's object spaces will be deemed the correct
-one.
+ Unlike Perl or Tcl, Python is not a "one-implementation" language, and
+ consequently the formal language specification should have priority
+ over the behavior of a particular implementation. The PyPy project
+ will reinforce this idea, and can be useful in sorting out ambiguities
+ in the specification. It is even possible that PyPy will eventually
+ serve as an "executable specification" for the language, and the
+ behavior of one of PyPy's object spaces will be deemed the correct
+ one.
---Guido van Rossum (home page: http://www.python.org/~guido/)
+ --Guido van Rossum (home page: http://www.python.org/~guido/)
In order to do this we will have to do something which is called
@@ -108,10 +108,11 @@
we would, obviously, have to submit a Standards Track PEP.
The complete details of how to write a PEP are themselves an
-Informational PEP -- PEP #1 in fact. A copy of PEP #1 is provided
+Informational PEP -- PEP #1 in fact. A copy of PEP #1 [PEP1]_ is provided
for convenience in this appendix:
-
-FIXME include http://www.python.org/peps/pep-0001.html
+
+.. [PEP1] http://www.python.org/peps/pep-0001.html
+.. FIXME grab it for appendix inclusion
After circulating through the community, PEPs are reviewed by Guido
van Rossum, the language author, and his chosen consultants, who may
More information about the Pypy-commit
mailing list