requirements/tests/files/test-project.txt
Sean Dague f7fbf480da one global-requirements.txt to rule them all
... and in the darkness bind them.

This moves the contents of requirements.txt and
test-requirements.txt to a single file, global-requirements.txt.
This means that regardless of whether a requirement is in
either file it will get checked. This massively simplifies the
checking and upgrading of req and test-req files.

This also adds in a unit testing framework for the update.py
script to ensure it does what we think it does. This is
accomplished by making a fake tree with a set of req and test-req
files, running update.py, and ensuring the updates were made
that we expected. It includes testing for the oslo url case,
as well as test-requires.

Change-Id: Ib9b86ade4cb8317509e218aec31f32e5d08f4035
2013-08-02 13:13:57 -04:00

19 lines
319 B
Plaintext

hacking>=0.5.6,<0.7
coverage>=3.6
discover
feedparser
fixtures>=0.3.12
mox==0.5.3
MySQL-python
psycopg2
pylint==0.25.2
# Imported by ldapdns so required to generate
# the sample configuration file
python-ldap==2.3.13
python-subunit
setuptools_git>=0.4
sphinx>=1.1.2
oslo.sphinx
testrepository>=0.0.13
testtools>=0.9.27