On Sat, Oct 13, 2012 at 6:21 AM, Adrian Holovaty <adr...@holovaty.com> wrote:
> Hi all,
>
> We've been talking about moving django.contrib.localflavor into
> separate packages, outside of Django proper
> (https://groups.google.com/d/topic/django-developers/OiyEGmXTifs/discussion).
> Today I did the work of creating the django-localflavor-* packages and
> copying code/tests/docs to them.
>
> Now we have 44 django-localflavor-* projects on our Django GitHub
> account, and you can see them here:
>
> https://github.com/django

w00t! Nice work, Adrian!

> Here are the outstanding to-dos with this effort:
>
> * Document a clear way to run the tests for a given
> django-localflavor-* package. I moved the tests into the separate
> packages, but there's no clear way to run them. Any suggestions?

The best option I've see for this sort of thing is tox:

http://tox.testrun.org/

This allows you to specify the PyPI packages (and versions) that need
to be installed in order to run the test suite, and automates the
process of setting up the test environment (using virtualenv). If code
needs to run as part of a larger project, tox can coordinate running
the tests in that project. It also integrates nicely with CI servers,
and it allows for easy testing across Python and Django versions.

To pick an example at random: here's the tox.ini file for
Easy-thumbnails, which tests Py2.5-Py2.7, Django 1.2-1.4, as well as
the documentation build.

https://github.com/SmileyChris/easy-thumbnails/blob/master/tox.ini

Russ %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to