Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8616
| Path | csiph.com!aioe.org!gothmog.csi.it!bofh.it!news.nic.it!robomod |
|---|---|
| From | Clint Byrum <spamaps@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 01:30:01 +0200 |
| Message-ID | <rNmel-eU-7@gated-at.bofh.it> (permalink) |
| References | <rNlBE-8bD-1@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Thu Jun 23 23:24:09 2016 |
| Old-Return-Path | <clint@fewbar.com> |
| X-Amavis-Spam-Status | No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -7 |
| X-Greylist | delayed 519 seconds by postgrey-1.35 at bendel; Thu, 23 Jun 2016 23:06:58 UTC |
| Content-Type | text/plain; charset=UTF-8 |
| User-Agent | Sup/0.22.1 |
| Content-Transfer-Encoding | 8bit |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/13949 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/1466722634-sup-3679@fewbar.com |
| Approved | robomod@news.nic.it |
| Lines | 19 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Thu, 23 Jun 2016 15:58:13 -0700 |
| X-Original-Message-ID | <1466722634-sup-3679@fewbar.com> |
| X-Original-References | <CAPzz3hbj+CnrtZ2WXB92BNtRk2PRfORoKdwdWNd868gtH0Rh6w@mail.gmail.com> |
| Xref | csiph.com linux.debian.maint.python:8616 |
Show key headers only | View raw
Excerpts from Neil Muller's message of 2016-06-24 00:26:25 +0200: > 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. > > Looking at some other packages in the archive, there seem to be > several approaches used to solve similar problems > > a) Bundle the application in both python2 and python3 version and use > alternatives to manage the version (docutils and sphinx, for example, > although in those cases the programs are used fairly extensively as > applications) This seems like the most reasonable method, and the one I'd expect as a user.
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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