Recipe to prevent django-setuptest from polluting module being tested with downloaded eggs
Project Description
Django Setuptest Recipe
Recipe to prevent django-setuptest from polluting module being tested with downloaded eggs.
Motivation
django-setuptest downloads eggs required for a test run and places them in the module directory. For example, if the module to be tested is called foo then the command python setup.py test causes src/foo to be polluted with many eggs. There is currently no way to instruct setuptools to store these eggs in another location.
django-setuptest-recipe addresses this shortcoming by wrapping the Python interpreter to be aware of egg locations.
Usage
Add the following to your buildout.cfg:
parts= ... setuptest-runner [setuptest-runner] recipe = django-setuptest-recipe eggs = ${buildout:eggs}
An executable file called setuptest-runner is created in the bin directory. You can now do /path/to/instance/bin/setuptest-runner setup.py test from within the src/foo directory.
Release history Release notifications
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Filename, size & hash SHA256 hash help | File type | Python version | Upload date |
---|---|---|---|
django_setuptest_recipe-0.1-py2.4.egg (4.0 kB) Copy SHA256 hash SHA256 | Egg | 2.4 | Aug 3, 2012 |
django_setuptest_recipe-0.1-py2.6.egg (4.0 kB) Copy SHA256 hash SHA256 | Egg | 2.6 | Oct 17, 2011 |
django-setuptest-recipe-0.1.tar.gz (2.5 kB) Copy SHA256 hash SHA256 | Source | None | Oct 17, 2011 |