[Zope-dev] RFC: adding support for testing from bare setuptools

Philipp von Weitershausen philipp at weitershausen.de
Wed Sep 17 18:42:33 EDT 2008


Marius Gedminas wrote:
> On Wed, Sep 17, 2008 at 12:52:49PM -0400, Tres Seaver wrote:
>> Proposal
>> --------
>>
>> Instead, what I *am* proposing is adding metadata which allows consumers
>> of such packages to verify that the package is downloaded / installed
>> correctly.  In particular, I want for the following scenario to work
>> seamlessly::
>>
>>  $ /path/to/virtualenv --no-site-packges sandbox
>>  ...
>>  $ cd sandbox
>>  $ tar xzf zope.foo.bar-3.5.6.tar.gz
>>  $ cd zope.foo.bar-3.5.6           # [1]
>>
>>  $ ../bin/python setup.py test     # [2]
>>  # Runs egg_info, installs regular and testing dependencies, and
>>  # runs all unit (non-layer) tests
> 
> I don't like the idea that running the tests installs additional
> packages into my environment without me explicitly asking for it.

You *are* asking for it by running python setup.py test. Also, python 
setup.py test doesn't actually install testing dependencies (or any 
dependencies for that matter) into site-packages. It just dumps them 
into the CWD.


More information about the Zope-Dev mailing list