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

Olemis Lang olemis at gmail.com
Thu Aug 12 05:14:21 PDT 2010

On Thu, Aug 12, 2010 at 4:04 AM, Fernando Perez <fperez.net at gmail.com> wrote:
> On Wed, Aug 11, 2010 at 12:38 AM, Ben Finney <ben+python at benfinney.id.au> wrote:
>> Fernando Perez <fperez.net at gmail.com> writes:
> Ultimately all I can say is that I have *extensive, real-world*
> evidence of this approach having worked *fantastically* well for
> ipython, numpy, scipy, nipy.*, etc over the last few years.

The same can be stated by people that don't include tests in packages
... so like I said , probably a matter of flavors + laziness + ... but
IMO that doesn't justify that in certain percent of the production
deployment environments the tests & testing libs deployed in there
will be definitely a decorative artifact >80% of the time , and do not
provide functionality to the end-users , but may be a way to get
support & communicate with the dev-team , something that can be
achieved by splitting the test package as well .



Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

More information about the testing-in-python mailing list