Hello.
Many Python modules ship unit tests which do not require module
instalation or user interaction and so can be run automatically during the
build time. They can be a very good QA tool, but it looks like they are
not used in all packages.
python-pylons: not used
python-pybabel: not used
pylin
FWIW I usually prefer to run unittests against (PYTHONPATH)
installed (debian/tmp/... if with extensions to be moved into -lib, or
debian/python-X/... for pure Python module) version to make sure that
everything got installed correctly. Also, if not too lengthy, I run
unittests against all suppor
On Feb 22, 2011, at 03:51 PM, Andrey Rahmatullin wrote:
>In many cases $PYTHON setup.py test (for all supported $PYTHON's) is
>enough to run the tests and any errors mean that something is wrong with
>the environment (provided the tests are correct).
>
>Shouldn't we have some written recommendatio
On 02/22/2011 03:47 PM, Barry Warsaw wrote:
It would be nice if dh auto-detected a setup.py (and/or missing Makefile) and
didn't run 'make test' in that case, so that the override_dh_auto_test wasn't
necessary. Yah, I should create a bug and patch for that.
I don;t think it would be a good id
On Feb 22, 2011, at 03:58 PM, Bernd Zeimetz wrote:
>On 02/22/2011 03:47 PM, Barry Warsaw wrote:
>
>> It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
>> and didn't run 'make test' in that case, so that the override_dh_auto_test
>> wasn't necessary. Yah, I should create a
On Tuesday, February 22, 2011 09:58:36 am Bernd Zeimetz wrote:
> On 02/22/2011 03:47 PM, Barry Warsaw wrote:
> > It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
> > and didn't run 'make test' in that case, so that the
> > override_dh_auto_test wasn't necessary. Yah, I sho
On Feb 22, 2011, at 11:17 AM, Scott Kitterman wrote:
>On Tuesday, February 22, 2011 09:58:36 am Bernd Zeimetz wrote:
>> On 02/22/2011 03:47 PM, Barry Warsaw wrote:
>> > It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
>> > and didn't run 'make test' in that case, so that t
On Tue, Feb 22, 2011 at 11:17:47AM -0500, Scott Kitterman wrote:
> > > It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
> > > and didn't run 'make test' in that case, so that the
> > > override_dh_auto_test wasn't necessary. Yah, I should create a bug and
> > > patch for t
On Tue, Feb 22, 2011 at 09:47:20AM -0500, Barry Warsaw wrote:
> It would be nice if dh auto-detected a setup.py (and/or missing Makefile) and
> didn't run 'make test' in that case, so that the override_dh_auto_test wasn't
> necessary. Yah, I should create a bug and patch for that.
Note that tests
OoO En cette fin de matinée radieuse du mardi 22 février 2011, vers
11:51, Andrey Rahmatullin disait :
> Many Python modules ship unit tests which do not require module
> instalation or user interaction and so can be run automatically during the
> build time. They can be a very good QA tool,
On Tue, Feb 22, 2011 at 07:23:51PM +0100, Vincent Bernat wrote:
> I wasn't aware of the existence of a test target.
It's a setuptools feature if I understand correctly
(setuptools.command.test) and it needs specific test* arguments to
setup(). Not all modules support it, some have custom runte
On Feb 22, 2011, at 11:27 PM, Andrey Rahmatullin wrote:
>On Tue, Feb 22, 2011 at 07:23:51PM +0100, Vincent Bernat wrote:
>> I wasn't aware of the existence of a test target.
>It's a setuptools feature if I understand correctly
>(setuptools.command.test) and it needs specific test* arguments t
On Feb 22, 2011, at 09:55 PM, Andrey Rahmatullin wrote:
>On Tue, Feb 22, 2011 at 09:47:20AM -0500, Barry Warsaw wrote:
>> It would be nice if dh auto-detected a setup.py (and/or missing Makefile)
>> and didn't run 'make test' in that case, so that the override_dh_auto_test
>> wasn't necessary. Ya
13 matches
Mail list logo
