From 31427dfed6a31e2a7ee647ef011c9a8dd392f5b8 Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Fri, 31 Mar 2006 10:38:30 +0000 Subject: [PATCH] it's -> its --- pep-0205.txt | 6 +++--- pep-0219.txt | 2 +- pep-0282.txt | 2 +- pep-0298.txt | 2 +- pep-0313.txt | 2 +- pep-0330.txt | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-) diff --git a/pep-0205.txt b/pep-0205.txt index eab2408b11e..32f1eb8ae51 100644 --- a/pep-0205.txt +++ b/pep-0205.txt @@ -50,8 +50,8 @@ Motivation Circular references - DOMs require a huge amount of circular (to parent & document - nodes), but these could be eliminated using a weak - dictionary mapping from each node to it's parent. This + nodes) references, but these could be eliminated using a weak + dictionary mapping from each node to its parent. This might be especially useful in the context of something like xml.dom.pulldom, allowing the .unlink() operation to become a no-op. @@ -291,7 +291,7 @@ Weak References in Java "Phantom" references are a little different; unlike weak and soft references, the referent is not cleared when the reference is - added to it's queue. When all phantom references for an object + added to its queue. When all phantom references for an object are dequeued, the object is cleared. This can be used to keep an object alive until some additional cleanup is performed which needs to happen before the objects .finalize() method is called. diff --git a/pep-0219.txt b/pep-0219.txt index 11847476153..19ce3db2cc6 100644 --- a/pep-0219.txt +++ b/pep-0219.txt @@ -115,7 +115,7 @@ Problems / microthreads. Generally, when a recursive call is transformed into a loop, a bit - of extra bookkeeping is required. The loop will need to keep it's + of extra bookkeeping is required. The loop will need to keep its own "stack" of arguments and results since the real stack can now only hold the most recent. The code will be more verbose, because it's not quite as obvious when we're done. While Stackless is not diff --git a/pep-0282.txt b/pep-0282.txt index 2acf3103959..f40b29b5595 100644 --- a/pep-0282.txt +++ b/pep-0282.txt @@ -324,7 +324,7 @@ Loggers def setLoggerClass(klass): ... - The passed class should be a subclass of Logger, and it's __init__ + The passed class should be a subclass of Logger, and its __init__ method should call Logger.__init__. diff --git a/pep-0298.txt b/pep-0298.txt index 14fcdba3fcd..04b5116f437 100644 --- a/pep-0298.txt +++ b/pep-0298.txt @@ -44,7 +44,7 @@ Specification The object must be unlocked again by releasing the buffer if it's no longer used by calling another function in the locked buffer interface. If the object never resizes or reallocates the buffer - during it's lifetime, this function may be NULL. Failure to call + during its lifetime, this function may be NULL. Failure to call this function (if it is != NULL) is a programming error and may have unexpected results. diff --git a/pep-0313.txt b/pep-0313.txt index 2abf71ac9c8..d58da350809 100644 --- a/pep-0313.txt +++ b/pep-0313.txt @@ -23,7 +23,7 @@ BDFL Pronouncement This PEP is rejected. While the majority of Python users deemed this to be a nice-to-have feature, the community was unable to reach a - concensus on whether nine should be represented as IX, the modern + consensus on whether nine should be represented as IX, the modern form, or VIIII, the classic form. Likewise, no agreement was reached on whether MXM or MCMXC would be considered a well-formed representation of 1990. A vocal minority of users has also requested diff --git a/pep-0330.txt b/pep-0330.txt index 10a6741f158..04ce44d3761 100644 --- a/pep-0330.txt +++ b/pep-0330.txt @@ -62,7 +62,7 @@ Motivation allow Python bytecode to execute arbitrary C-level machine instructions or to modify private, internal data structures in the interpreter. If used cleverly this could subvert any form of - security policy an application may want to apply to it's objects. + security policy an application may want to apply to its objects. Practically, it would be difficult for a malicious user to "inject" invalid bytecode into a PVM for the purposes of