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

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

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

Show all headers | 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

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