Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14867

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

Cross-posted to 2 groups.

Show key headers only | View raw

Do we really have to have this argument again?  Let's not.  Please wontfix and let's move on.

Personally, I maintain 25 packages in the team that would need renaming.  I'm not sure how many total there are, but they'd all have to go through New again.

It'd be much simpler just to drop DPT or myself from uploaders and ignore this, so that's probably the path I would take.

Regardless, I don't think this is an appropriate use of FTP Team time/energy.

Also, as I've said before on this topic, every packaging rule is a barrier to entry for new contributors.  We really shouldn't add things that aren't needed.

Scott K

On January 29, 2023 12:57:37 AM UTC, Guillem Jover <guillem@debian.org> wrote:
>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
>

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#791635: python-policy: Please require namespacing source python module packages Guillem Jover <guillem@debian.org> - 2023-01-29 02:10 +0100
  Re: Bug#791635 python-policy: Please require namespacing source python module packages Scott Kitterman <debian@kitterman.com> - 2023-01-29 02:40 +0100
    Re: Bug#791635 python-policy: Please require namespacing source  python module packages Stefano Rivera <stefanor@debian.org> - 2023-02-06 15:30 +0100

csiph-web