requirements/tests
Sean Dague 38b7490667 provide more meaningful output on update.py
In an attempt to make the proposal bot changes for requirements be
more meaningful make the update.py script return something that's more
user friendly.

Now by default the script will return the following to stdout on success:

Version change for: mox, mox3, testrepository, testtools
Updated project/test-requirements.txt:
    mox==0.5.3                     ->   mox>=0.5.3
    mox3==0.7.3                    ->   mox3>=0.7.0
    testrepository>=0.0.13         ->   testrepository>=0.0.17
    testtools>=0.9.27              ->   testtools>=0.9.32

Add a verbose flag that will provide much of the previous debug info.

Eliminate the giant dict dump of all the requirements files, as that
was largely impossible to make sense of, and rarely provided any
insight. During a devstack run you'll have git hashes for all the
trees, so can track down exact file contents if needed.

By making this the default stdout we can then capture and use this for
the git commit messages.

In order to make the test output matching human readable ignore the 80
column limit for the expected blocks via #noqa.

Change-Id: I85604db7bffafcd20bf3cc546fe3e5d7bda72193
2015-01-08 16:18:26 -05:00
..
files Bump minimum required version for simplejson to 2.2.0 2014-08-23 16:49:30 -07:00
__init__.py one global-requirements.txt to rule them all 2013-08-02 13:13:57 -04:00
test_update.py provide more meaningful output on update.py 2015-01-08 16:18:26 -05:00
test_update_pbr.py Bump hacking to version 0.9.2 2014-07-16 15:57:40 +02:00
test_update_suffix.py Bump hacking to version 0.9.2 2014-07-16 15:57:40 +02:00
test_versions_overlap_parent.py Add a tox env to check requirements overlap 2014-08-25 16:27:18 -05:00