[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#791635 python-policy: Please require namespacing source python module packages



Control: reopen -1
Control: reassign -1 python3

[ Sorry, resending, as the bug was archived so it ignored all the
  control commands. ]

This got closed due to the python-defaults package being removed from
sid, reopening and reassigning where python-policy seems to be located
now.

On Tue, 2022-12-27 at 23:29:30 +0000, Debian Bug Tracking System wrote:
> Date: Tue, 7 Jul 2015 03:11:06 +0200
> From: Guillem Jover <guillem@debian.org>
> To: submit@bugs.debian.org
> Subject: python-policy: Please require namespacing source python module
>  packages
> Message-ID: <20150707011106.GA12809@gaara.hadrons.org>
> User-Agent: Mutt/1.5.23 (2014-03-12)
> X-Spam-Status: No, score=-6.6 required=4.0 tests=BAYES_00,FROMDEVELOPER,
>  RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD autolearn=ham autolearn_force=no
>  version=3.4.0-bugs.debian.org_2005_01_02
> 
> Source: python-defaults
> Source-Version: 2.7.9-1
> Severity: wishlist
> 
> Hi!
> 
> Given recent ITP discussions [0] about lack of namespacing on python
> module source package names, I think it would be really good to fix
> this at the source, by mandating it in the python-policy. Attached is
> a proposal wording.
> 
>   [0] #748383: ITP: bash8; #745347: ITP: releases; #790399: ITP: structlog
> 
> Thanks,
> Guillem

> === modified file 'debian/python-policy.sgml'
> --- debian/python-policy.sgml	2015-02-27 23:09:27 +0000
> +++ debian/python-policy.sgml	2015-07-06 19:58:13 +0000
> @@ -513,7 +513,9 @@
>  	  to use this prefix for all packages with public modules as they may
>  	  be used by other packages in the future.  Python 3 modules must be
>  	  in a separate binary package prefixed with <var>python3-</var> to
> -	  preserve run time separation between python and python3.
> +	  preserve run time separation between python and python3.  When the
> +	  source package only produces python module binary packages, it must
> +	  also be prefixed with <var>python-</var>.
>  
>  	  The binary package for module foo should preferably be named
>  	  <package>python-<var>foo</var></package>, if the module name
> 

Thanks,
Guillem


Reply to: