Re: running tests against installed version of package

2016-04-06 Thread Piotr Ożarowski
[Thomas Goirand, 2016-04-06] > Don't use py.test-FOO, as this is deprecated. Instead, use something > like this: > > PYTHON3S:=$(shell py3versions -vr) > > override_dh_auto_test: > ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS))) > @echo "===> Running tests" > set -e ; set -x ;

Re: Packaging Grip

2016-04-06 Thread Dmitry Shachnev
Hi Tiago, On Mon, Apr 04, 2016 at 04:29:44PM -0300, Tiago Ilieve wrote: > Hi, > > The Style Guide for Packaging Python Libraries[1] states that in cases > like this, one should package the library for both Python 2 and 3, > creating a third package that contains the executable. As this package > i

request for alioth team

2016-04-06 Thread Adrian Alves
Hello guy, my name is Adrian i want to be part of the python-modules team in alioth i have a few pkgs in mentors for review and also i want to start fixing some of the pkgs that you have already, i did it for python-clicks and sent it to av...@debian.org but i want to start collaboration with the t

Re: Packaging Grip

2016-04-06 Thread Tiago Ilieve
Hi Dmitry, On 6 April 2016 at 17:21, Dmitry Shachnev wrote: > 1. Public (/usr/lib/python*/dist-packages) vs private (/usr/share/) location > depends on whether the module is intended to be used by third-party packages, > or only by grip itself. > > 2. The Style Guide doesn't *require* both Python

Re: Packaging Grip

2016-04-06 Thread Scott Kitterman
On April 6, 2016 10:37:24 PM EDT, Tiago Ilieve wrote: >Hi Dmitry, > >On 6 April 2016 at 17:21, Dmitry Shachnev wrote: >> 1. Public (/usr/lib/python*/dist-packages) vs private (/usr/share/) >location >> depends on whether the module is intended to be used by third-party >packages, >> or only by