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

2016-06-23 Thread Ben Finney
Neil Muller 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 t

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

2016-06-23 Thread Clint Byrum
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 b

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

2016-06-23 Thread Neil Muller
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 g

Re: Python package providing both modules and an app

2016-06-23 Thread Hugo Lefeuvre
> > The entry point is generated by 'setup.py install_scripts', which is > > executed by pybuild after files specified in *.install have been > > installed (correct me if I'm wrong). > > I haven't demonstrated for this case, but I would be surprised if that's > how it behaves. To my mind the ‘setu