[Python-checkins] r46611 - peps/trunk/pep-0339.txt peps/trunk/pep-0347.txt peps/trunk/pep-0355.txt
george.yoshida
python-checkins at python.org
Sat Jun 3 19:20:13 CEST 2006
Author: george.yoshida
Date: Sat Jun 3 19:20:12 2006
New Revision: 46611
Modified:
peps/trunk/pep-0339.txt
peps/trunk/pep-0347.txt
peps/trunk/pep-0355.txt
Log:
Repair typos
Modified: peps/trunk/pep-0339.txt
==============================================================================
--- peps/trunk/pep-0339.txt (original)
+++ peps/trunk/pep-0339.txt Sat Jun 3 19:20:12 2006
@@ -29,7 +29,7 @@
Starting with Python 2.5, the above steps are now used. This change
was done to simplify compilation by breaking it into three steps.
-The purpose of this document is to outline how the lattter three steps
+The purpose of this document is to outline how the latter three steps
of the process works.
This document does not touch on how parsing works beyond what is needed
@@ -515,7 +515,7 @@
changed.
* pycodegen.py
- One of the files that muc be modified if Include/opcode.h is
+ One of the files that must be modified if Include/opcode.h is
changed.
Modified: peps/trunk/pep-0347.txt
==============================================================================
--- peps/trunk/pep-0347.txt (original)
+++ peps/trunk/pep-0347.txt Sat Jun 3 19:20:12 2006
@@ -56,8 +56,8 @@
operators could not always respond in a timely manner. In particular,
for CVS, they had to reduce the load on the primary CVS server by
introducing a second, read-only CVS server for anonymous access. This
-server is regularly synchronized, but lags behind the the read-write
-CVS repository between synchronizations. As a result, users without
+server is regularly synchronized, but lags behind the read-write CVS
+repository between synchronizations. As a result, users without
commit access can see recent changes to the repository only after a
delay.
Modified: peps/trunk/pep-0355.txt
==============================================================================
--- peps/trunk/pep-0355.txt (original)
+++ peps/trunk/pep-0355.txt Sat Jun 3 19:20:12 2006
@@ -33,7 +33,7 @@
were made to get the path module included in the Python standard
library; [4], [5], [6], [7].
- This PEP summarizes the the ideas and suggestions people have
+ This PEP summarizes the ideas and suggestions people have
expressed about the path module and proposes that a modified
version should be included in the standard library.
@@ -107,7 +107,7 @@
the manipulation of file contents, for which file objects are
better suited.
- - Platform incompatibilites are dealt with by not instantiating
+ - Platform incompatibilities are dealt with by not instantiating
system specific methods.
@@ -389,7 +389,7 @@
* The __div__() method was removed. Overloading the / (division)
operator may be "too much magic" and make path concatenation
appear to be division. The method can always be re-added later
- if the BFDL so desires. In its place, __new__() got an *args
+ if the BDFL so desires. In its place, __new__() got an *args
argument that accepts both Path and string objects. The *args
are concatenated with os.path.join() which is used to construct
the Path object. These changes obsoleted the problematic
@@ -429,7 +429,7 @@
should it live? In its own module or in os?
* Due to Path subclassing either str or unicode, the following
- non-magic, public methods are availible on Path objects:
+ non-magic, public methods are available on Path objects:
capitalize(), center(), count(), decode(), encode(),
endswith(), expandtabs(), find(), index(), isalnum(),
@@ -525,7 +525,7 @@
References and Footnotes
- [1] Method is not guaranteed to be availible on all platforms.
+ [1] Method is not guaranteed to be available on all platforms.
[2] "(idea) subclassable string: path object?", van Rossum, 2001
http://mail.python.org/pipermail/python-dev/2001-August/016663.html
More information about the Python-checkins
mailing list