[TIP] including (or not) tests within your package

[Barry Warsaw]

On Jul 28, 2010, at 07:49 AM, Olemis Lang wrote:

>>> +1 for including the tests by default.
>>>
>>
>> Agreed 100x with Barry -
>
>IMO, tests shouldn't be installed in production systems ...

It's certainly within the decisions of platform packagers to separate tests
from the code, but I'd argue that it's not worth it.  I just don't see what
advantage *not* including the tests gives you.  And arguably it can make for
more complicated packaging, especially when those tests are in-tree, which is
usually how I structure my development branches.

Sure, there are exceptions, and big frameworks/packages might want to do
things differently.  But I'd argue that the *majority* of Python packages are
fairly simple and straightforward and it's better (and easier!) to just
include the tests.

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20100729/415550a3/attachment.pgp>