Re: When packaging a library, should I prevent its test suite from being packaged

To: debian-python@lists.debian.org
Subject: Re: When packaging a library, should I prevent its test suite from being packaged
From: Tianon Gravi <admwiggin@gmail.com>
Date: Wed, 10 Sep 2014 09:49:42 -0600
Message-id: <[🔎] CAHnKnK3DX4ZBiWqFLeKtrvkL_0j0_KTuj7CZ-PCxnKQJ5zSODg@mail.gmail.com>
In-reply-to: <[🔎] 20140909152825.GY4404@sts0.p1otr.com>
References: <[🔎] 20140909185320.89183bfff8ff6a48ebdbb985@domain007.com> <[🔎] 20140909152825.GY4404@sts0.p1otr.com>

On 9 September 2014 09:28, Piotr Ożarowski <piotr@debian.org> wrote:
> (I will remove all .../dist-packages/test{,s} by default in next
> dh_python{2,3} version).

Does this mean we'll get a nice warning too, so we know that we need
to report the bug upstream? :)

♥,
- Tianon

Reply to:

Follow-Ups:
- Re: When packaging a library, should I prevent its test suite from being packaged
  - From: Piotr Ożarowski <piotr@debian.org>

References:
- When packaging a library, should I prevent its test suite from being packaged
  - From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
- Re: When packaging a library, should I prevent its test suite from being packaged
  - From: Piotr Ożarowski <piotr@debian.org>

Prev by Date: Re: Python applications: private dirs and PYTHONPATH issue
Next by Date: Re: Python applications: private dirs and PYTHONPATH issue
Previous by thread: Re: When packaging a library, should I prevent its test suite from being packaged
Next by thread: Re: When packaging a library, should I prevent its test suite from being packaged
Index(es):
- Date
- Thread