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
=== 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.
-	  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 id="specifying_versions">
 	<heading>Specifying Supported Versions</heading>

Reply via email to