Skip to main content

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.

Authors

Praekelt Foundation

  • Hedley Roos

Changelog

0.1

  1. First release.

Project details


Release history Release notifications | RSS feed

This version

0.1

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-setuptest-recipe-0.1.tar.gz (2.5 kB view hashes)

Uploaded Source

Built Distributions

django_setuptest_recipe-0.1-py2.6.egg (4.0 kB view hashes)

Uploaded Source

django_setuptest_recipe-0.1-py2.4.egg (4.0 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page