Add clarification of naming requirements for submocules (Closes: #701192)

debian/changelog

@@ -15,6 +15,7 @@ python-defaults (2.7.7-1) UNRELEASED; urgency=medium
     - Thanks to Peter Pentchev for the patch
   * Drop unused build-depends on libhtml-tree-perl
   * Clarify discussion of requirement to use python:Provides (Closes: #669346)
+  * Add clarification of naming requirements for submocules (Closes: #701192)
 
  -- Matthias Klose <doko@debian.org>  Mon, 02 Jun 2014 19:54:25 +0200
 

debian/python-policy.sgml

@@ -36,7 +36,7 @@
         <name>Barry Warsaw</name>
         <email>barry@debian.org</email>
       </author>
-      <version>version 0.10.0</version>
+      <version>version 0.10.0.1</version>
 
       <abstract>
 	This document describes the packaging of Python within the
@@ -122,11 +122,6 @@
 	  </item>
 	</enumlist></p>
 
-	<p>
-	  Python 3 (3.1) was released in June 2009, and is available in
-	  the Debian 6.0 (squeeze) release (3.1), and in the Debian 7
-	  (wheezy) release (3.2).
-	</p>
     </chapt>
 
     <chapt id="python">
@@ -526,6 +521,10 @@
 	  multiple modules.  In the latter case the maintainer chooses the
 	  name of the module which represents the package the most.
 
+          For subpackages such as <var>foo.bar</var>, the recommendation is to
+          name the binary packages <package>python-<var>foo.bar</var></package>
+          and <package>python3-<var>foo.bar</var></package>.
+
 	  Such a package should support the current Debian Python version,
 	  and more if possible (there are several tools to help implement
 	  this, see <ref id="packaging_tools">). For example, if Python 2.5,