From 5740920bb392ec6e0bc5f2e3949a37b3bf8519d9 Mon Sep 17 00:00:00 2001 From: Ruby Loo Date: Wed, 22 May 2013 20:12:08 +0000 Subject: Rename requires files to standard names. Rename tools/pip-requires to requirements.txt and tools/test-requires to test-requirements.txt. These are standard files, and tools in the general world are growing intelligence about them. Change-Id: I68ece8406fb1d4e082a42db8e76e17b1aaa7e775 Fixes: bug #1179008 --- doc/source/devref/development.environment.rst | 2 +- doc/source/devref/unit_tests.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/source/devref/development.environment.rst b/doc/source/devref/development.environment.rst index 8c6e03323..79c368d3a 100644 --- a/doc/source/devref/development.environment.rst +++ b/doc/source/devref/development.environment.rst @@ -123,7 +123,7 @@ You can manually install the virtual environment instead of having python tools/install_venv.py This will install all of the Python packages listed in the -``tools/pip-requires`` file into your virtualenv. There will also be some +``requirements.txt`` file into your virtualenv. There will also be some additional packages (pip, distribute, greenlet) that are installed by the ``tools/install_venv.py`` file into the virutalenv. diff --git a/doc/source/devref/unit_tests.rst b/doc/source/devref/unit_tests.rst index 8033406f0..b6549bd00 100644 --- a/doc/source/devref/unit_tests.rst +++ b/doc/source/devref/unit_tests.rst @@ -100,7 +100,7 @@ If you wish to recreate the virtualenv, call ``run_tests.sh`` with the flag:: -f, --force Recreating the virtualenv is useful if the package dependencies have changed -since the virtualenv was last created. If the ``tools/pip-requires`` or +since the virtualenv was last created. If the ``requirements.txt`` or ``tools/install_venv.py`` files have changed, it's a good idea to recreate the virtualenv. -- cgit