Remove the .clear() method; add a link to the patch on SF.

pep-0205.txt

@@ -5,7 +5,7 @@ Author: Fred L. Drake, Jr. <fdrake@acm.org>
 Python-Version: 2.1
 Status: Incomplete
 Type: Standards Track
-Post-History: 
+Post-History: 11 January 2001
 
 Motivation
 
@@ -81,14 +81,11 @@ Proposed Solution
     weakref.mapping() will create a "weak dictionary".
 
     A weak reference object will allow access to the referenced object
-    if it hasn't been collected, allows application code to either
-    "clear" the weak reference and the associated callback, and to
-    determine if the object still exists in memory.  These operations
-    are accessed via the .get(), .clear(), and .islive() methods.  If
-    the object has been collected, .get() will return None and
-    islive() will return false; calling .clear() will produce the same
-    result, and is allowed to occur repeatedly.  Weak references are
-    not hashable.
+    if it hasn't been collected and to determine if the object still
+    exists in memory.  These operations are accessed via the .get()
+    and .islive() methods.  If the object has been collected, .get()
+    will return None and islive() will return false.  Weak references
+    are not hashable.
 
     A weak dictionary maps arbitrary keys to values, but does not own
     a reference to the values.  When the values are finalized, the
@@ -142,6 +139,10 @@ Implementation Strategy
     dictionaries.  Whether it should include strings, buffers, lists,
     files, or sockets is debatable.
 
+    There is a preliminary patch on SourceForge:
+
+    http://sourceforge.net/patch/?func=detailpatch&patch_id=103203&group_id=5470
+
 
 Possible Applications