requirements

History

Hervé Beraud fac394f79c Stop to use the __future__ module. The __future__ module [1] was used in this context to ensure compatibility between python 2 and python 3. We previously dropped the support of python 2.7 [2] and now we only support python 3 so we don't need to continue to use this module and the imports listed below. Imports commonly used and their related PEPs: - `division` is related to PEP 238 [3] - `print_function` is related to PEP 3105 [4] - `unicode_literals` is related to PEP 3112 [5] - `with_statement` is related to PEP 343 [6] - `absolute_import` is related to PEP 328 [7] [1] https://docs.python.org/3/library/__future__.html [2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html [3] https://www.python.org/dev/peps/pep-0238 [4] https://www.python.org/dev/peps/pep-3105 [5] https://www.python.org/dev/peps/pep-3112 [6] https://www.python.org/dev/peps/pep-0343 [7] https://www.python.org/dev/peps/pep-0328 Change-Id: I15d451f6a832b2e698b28e7351a36ef7aea92abe		2020-06-02 20:56:04 +02:00
..
babel-test.sh	Babel Integration tests	2016-04-24 17:21:18 -05:00
build_wheels.sh	Add a bashate tox environment and address errors	2017-09-28 12:09:04 +10:00
cap.py	Fix "wrap functions with 2 blank lines" pep8 check	2016-11-16 18:52:03 +08:00
check-install.py	Stop to use the __future__ module.	2020-06-02 20:56:04 +02:00
code-search.sh	[tools] Add a tool to grep local repos	2018-01-10 11:59:08 +11:00
cruft.sh	Replace openstack.org git:// URLs with https://	2019-03-24 20:36:01 +00:00
fix-lower-constraints.py	Fix typo in fix-lower-constraints.py	2018-06-07 12:30:41 -04:00
functions	Add tool to generate a health report for all reqs	2020-05-08 11:14:54 -05:00
get-health-report.sh	Add tool to generate a health report for all reqs	2020-05-08 11:14:54 -05:00
grep-all.sh	[tools/grep-all] Hide eol releases by default	2018-09-12 13:26:19 +10:00
list-unused-packages.sh	Add tool to generate a health report for all reqs	2020-05-08 11:14:54 -05:00
noop-change.sh	[tools] Add a tool to make a no-op change	2017-10-12 13:42:59 +11:00
publish_constraints.sh	[tools] include newton-eol in tools/publish_constraints.sh	2018-02-14 18:42:23 +11:00
README.txt	Remove requirements-integration job	2019-11-12 11:02:50 -06:00
what-broke.py	Trivial: Update pypi url to new url	2018-04-21 02:32:36 +00:00

README.txt

OpenStack Requirements tools.

This directory contains a number of tools that are useful to the requirements core team and OpenStack
developers.

babel-test.sh
-------------
A tool check for regressions with new Babel releases.

build_wheels.sh
---------------

Generate wheels for all of the requirements, ignoring any packages
that won't build wheels so we get as many as possible. This is meant
to be used on a development box combined with devpi and a wheelhouse
configuration setting for pip, such as described in
https://www.berrange.com/posts/2014/11/14/faster-rebuilds-for-python-virtualenv-trees/

cap.py
------

Take the output of 'pip freeze' and use the installed versions to caps requirements.

check-install.py
----------------

Used in tox environment pip-install. Only installs requirements (as opposed to
test-requirements and verifies that all console-scripts have all modules
needed.

code-search.sh
--------------
Assuming you have a set of local git repos grep them all for interesting things.

cruft.sh
--------

This script, when run from the root directory of this repository, will search
the default and feature branches of all projects listed in the projects.txt
file for declared dependencies, then output a list of any entries in the
global-requirements.txt file which are not actual dependencies of those
projects. Old dependencies which were removed from projects or which were used
only for projects which have since been removed should be cleaned up, but many
entries likely represent recent additions which still have pending changes to
add them to one or more projects. In most cases, git pickaxe will yield the
answer.

grep-all.sh
-----------

List a requirements specification and constratint for a given libarary

noop-change.sh
--------------

Generate a bulk no-op changes in supplied projects. Useful if we have a risky
change in global-requirements or upper-constraints and we want to test impacted
projects.

publish_constraints.sh
----------------------
Used in the gate! Generate the constraints files from git for publishing to a
static server.

what-broke.py
-------------
figure out what requirements change likely broke us.