On Sunday, June 20, 2010 03:54:30 pm Scott Kitterman wrote: > On Saturday, June 19, 2010 07:06:35 am Bernd Zeimetz wrote: > > On 06/18/2010 07:11 PM, Scott Kitterman wrote: > > > I don't think we need a new debian/control field to achieve the > > > separation. pyversions (as of yesterday's upload) ignores any python3 > > > versions it gets and py3versions ignores anything less than 3. > > > > +1. > > > > Adding more control fields just makes the mess bigger. > > I'm going to declare rough consensus around this approach and I'll have a > Python policy patch for review shortly. > > Scott K Patch attached. Comments please. Is it sufficient? Is it correct? Scott K
=== modified file 'debian/python-policy.sgml' --- debian/python-policy.sgml 2010-06-20 20:02:49 +0000 +++ debian/python-policy.sgml 2010-06-20 20:21:04 +0000 @@ -438,24 +438,35 @@ in the general paragraph (the first one, for the source package) of <file>debian/control</file> specifies the versions of Python supported by the source package. When not specified, it defaults to - all currently supported Python versions. - + all currently supported Python versions (Note: This does not include any + Python 3 versions). + </p> + <p> + It is used to express both Python and Python 3 versions. Support for + Python 3 versions cannot be implicitly defined, it must always be + explicit. It is not necessary to express <tt><< 3.0</tt> because this is + always true when Python versions are specified. + </p> + <p> It is notably used to track packages during Python transitions, and is also used by some packaging scripts to automatically generate appropriate Depends and Provides lines. The format of the field may be one of the following: <example> XS-Python-Version: >= X.Y +XS-Python-Version: >= 2.Y, >= 3.Y XS-Python-Version: >= A.B, << X.Y XS-Python-Version: A.B, X.Y XS-Python-Version: all +XS-Python-Version: all, >= 3.1 </example> The keyword "all" means that the package supports any Python version available but might be deprecated in the future since using version numbers is clearer than "all" and encodes more information. The keyword "all" is limited to Python versions and must be ignored for Python 3 versions. - + </p> + <p> The keyword "current" has been deprecated and used to mean that the package would only have to support a single version (even across default version changes). It must be ignored for Python 3
Attachment:
signature.asc
Description: This is a digitally signed message part.