Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Binary naming for Django Related Packages
Date: Wed, 18 Jan 2017 07:50:01 +0100
Message-ID: <t0Sed-D1-1@gated-at.bofh.it>
References: <sIwOR-4kz-5@gated-at.bofh.it> <sJ5tg-1Kz-13@gated-at.bofh.it> <sLHXr-7qQ-23@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Wed Jan 18 06:46:21 2017
Old-Return-Path: <debian@kitterman.com>
X-Amavis-Spam-Status: No, score=-7.1 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5
Dkim-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1484721964; bh=Upuf/78w+5wWLPxP5UirzZbU0uAFCiK0UTmZQ2gTYME=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YAr1W7jCJcGCkGO5Mj26VMxUawRxF/nI9QEDDnrGo5LZ2Fdu1aDbJWziCDGwDVQ5r EP/qSjiLryZTIEy/C631m548fUoDaDBxWzM/FrT33m56rdOfeuUy1/Oi9n8GkVy43e bIVe8CuT0vIRpILg1A9V48uNkXA/zFF+JMeQDcEc=
User-Agent: KMail/4.13.3 (Linux/3.13.0-106-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nextPart2880321.ZF77WuFs1v"
Content-Transfer-Encoding: 7Bit
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/14524
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/2082395.q8P2N71EsN@kitterma-e6430
Approved: robomod@news.nic.it
Lines: 68
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Wed, 18 Jan 2017 01:46:04 -0500
X-Original-Message-ID: <2082395.q8P2N71EsN@kitterma-e6430>
X-Original-References: <26917154.d0blnEnNDW@kitterma-e6430> <6385302.kCrYn87lNQ@kitterma-e6430> <20161207104329.zdyhm7tidek3ylgh@home.ouaza.com>
Xref: csiph.com linux.debian.maint.python:9169

This is a multi-part message in MIME format.

--nextPart2880321.ZF77WuFs1v
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Wednesday, December 07, 2016 11:43:29 AM Raphael Hertzog wrote:
> Hi,
> 
> On Wed, 30 Nov 2016, Scott Kitterman wrote:
> > Raphael, do you think that the upstream Django project might be willing to
> > make some kind of best practices for naming third party django packages? 
> > If they did that, then that would give us a basis for Debian maintainers
> > talking to their upstreams about moving to django_.
> 
> They already partly do that, see:
> https://docs.djangoproject.com/en/1.10/intro/reusable-apps/#packaging-your-a
> pp
> 
> They recommend a "django-" prefix in the PyPi package name. But they say
> nothing about the Python module name and the sample just bundles a "polls"
> module in a "django-polls" package.
> 
> Thus I posted this to gather their feedback on the need to recommend the
> prefix on the name of the module too:
> https://groups.google.com/forum/#!topic/django-developers/f8yNRkn6Fpo

Thanks.  Since not everyone liked my first attempt at this, I softened it a 
bit (please see the attached).  We're going to have at least one more python-
defaults upload and I'd like to get this resolved.

Scott K
--nextPart2880321.ZF77WuFs1v
Content-Disposition: attachment; filename="policy.patch"
Content-Transfer-Encoding: 7Bit
Content-Type: text/x-patch; charset="UTF-8"; name="policy.patch"

=== modified file 'debian/python-policy.sgml'
--- debian/python-policy.sgml	2016-11-26 07:23:09 +0000
+++ debian/python-policy.sgml	2017-01-18 06:39:18 +0000
@@ -628,14 +628,16 @@
 	  versions should be included in a single package.
 	</p>
 	<p>
-	  As a special exception to the  <package>python3-</package> and
-	  <package>python-</package> binary naming policy, Python modules
-	   intended for use  with Django (<package>python3-django</package>/
-	  <package>python-django</package>) should add django to their binary
-	  package names to make it clear they are intended for use with Django
-	  and not general purpose Python modules, i.e.
-	  <package>python3-django-</package> and
-	  <package>python-django-</package> respectively.
+          Packages intended for use with Django (<package>python3-django</package>/
+          <package>python-django</package>) are installed in the same namespace as
+          other python packages for a variety of reasons.  Many such packages are
+          named django_packagename upstream.  These are then packaged as
+          <package>python3-django-package</package> and
+          <package>python-django-package</package>.
+          This makes it clear that they are intended for use with Django
+          and not general purpose Python modules.  Debian maintainers are
+          encouraged to work with their upstreams to support consistent use of
+          this approach.
       </sect>
       <sect id="specifying_versions">
 	<heading>Specifying Supported Versions</heading>


--nextPart2880321.ZF77WuFs1v--