[Python-checkins] devguide: Some clarifications as suggested by Sean Reifschneider.

[brett.cannon]

brett.cannon pushed fa8332a76771 to devguide:

http://hg.python.org/devguide/rev/fa8332a76771
changeset:   100:fa8332a76771
user:        Brett Cannon <brett at python.org>
date:        Mon Jan 17 12:01:30 2011 -0800
summary:
  Some clarifications as suggested by Sean Reifschneider.

files:
  patch.rst
  stdlibchanges.rst

diff --git a/patch.rst b/patch.rst
--- a/patch.rst
+++ b/patch.rst
@@ -32,7 +32,9 @@
 Third, make sure you have proper tests to verify your patch works as expected.
 Patches will not be accepted without the proper tests!
 
-Fourth, if you are not already in the ``Misc/ACKS`` file then add your name. If
+Fourth, proper documentation additions/changes should be included.
+
+Fifth, if you are not already in the ``Misc/ACKS`` file then add your name. If
 you have taken the time to diagnose a problem, invent a solution, code it up,
 and submit a patch you deserve to be recognized as having contributed to
 Python. This also means you need to fill out a `contributor form`_ which
diff --git a/stdlibchanges.rst b/stdlibchanges.rst
--- a/stdlibchanges.rst
+++ b/stdlibchanges.rst
@@ -81,8 +81,10 @@
 Requirements
 ''''''''''''''
 In order for a module to even be considered for inclusion into the stdlib, a
-couple requirements must be met. The most basic is that the code must meet the
-same requirements as that of any other :ref:`patch <patch>`. For code that has
+couple requirements must be met.
+
+The most basic is that the code must meet
+:ref:`standard patch requirements <patch>`. For code that has
 been developed outside the stdlib typically this means making sure the coding
 style guides are followed and that the proper tests have been written.
 

--
Repository URL: http://hg.python.org/devguide