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

Re: Best practice for adding python3 version to existing module with helper programs?

Path	csiph.com!weretis.net!feeder6.news.weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From	Barry Warsaw <barry@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Best practice for adding python3 version to existing module with helper programs?
Date	Fri, 24 Jun 2016 15:40:01 +0200
Message-ID	<rNzuV-cP-17@gated-at.bofh.it> (permalink)
References	<rNlBE-8bD-1@gated-at.bofh.it> <rNs0p-42y-9@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Fri Jun 24 13:30:48 2016
Old-Return-Path	<barry@debian.org>
X-Amavis-Spam-Status	No, score=-6 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, GMAIL=1, LDO_WHITELIST=-5] autolearn=no autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5
Organization	The Organization of Unorganized Woozalists
X-Mailer	Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	quoted-printable
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13951
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/20160624093029.3f0e44bb.barry@wooz.org
Approved	robomod@news.nic.it
Lines	27
Sender	robomod@news.nic.it
X-Original-Date	Fri, 24 Jun 2016 09:30:29 -0400
X-Original-Message-ID	<20160624093029.3f0e44bb.barry@wooz.org>
X-Original-References	<CAPzz3hbj+CnrtZ2WXB92BNtRk2PRfORoKdwdWNd868gtH0Rh6w@mail.gmail.com> <858txvw3v8.fsf@benfinney.id.au>
Xref	csiph.com linux.debian.maint.python:8618

Show key headers only | View raw

On Jun 24, 2016, at 03:30 PM, Ben Finney wrote:

>Neil Muller <drnlmuller+python@gmail.com> writes:
>
>> I'm working on packaging the latest version of sqlobject, which adds
>> supprt for python 3, and I'm unsure of how best to handle the helper
>> applications that ship as part of the package. The helper applications
>> will work with both python2 and python3, so it's not clear to me how
>> to apply the advice given in [1], and I'd ideally want the helper
>> programs available regardless of which version of the module is
>> installed.  
>
>What is the purpose of the helper applications? Is there a significant
>use case for “I want specifically the Python 2 version of this
>application”?
>
>If not, I would advise making only the Python 3 applications available,
>in a separate binary package (and put it it “Section: database”) which
>describes the purpose without mentioning Python versions.

I concur with Ben.  If the end user won't care whether Python 2 or 3 is used
and the helper works the same regardless of which Python invokes it, please
just ship the Python 3 version.  It should go in a separate binary package.

Cheers,
-Barry

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

Thread

Best practice for adding python3 version to existing module with  helper programs? Neil Muller <drnlmuller+python@gmail.com> - 2016-06-24 00:50 +0200
  Re: Best practice for adding python3 version to existing module with helper programs? Clint Byrum <spamaps@debian.org> - 2016-06-24 01:30 +0200
  Re: Best practice for adding python3 version to existing module with helper programs? Ben Finney <ben+debian@benfinney.id.au> - 2016-06-24 07:40 +0200
    Re: Best practice for adding python3 version to existing module  with helper programs? Barry Warsaw <barry@debian.org> - 2016-06-24 15:40 +0200

csiph-web