releases/requirements.txt
Sean McGinnis 5359acf788
Use recommended twine check for README validation
The use of ``python setup.py check -r -s`` is actually deprecated and
the recommended method for validating a README for PyPi upload is to
build the sdist and wheel and run ``twine check $DIST_PATH``. This
switches our validation check to use the supported method.

Change-Id: I321b8cf6f1e2116d2fe23059d5f13aa6f2ae8b4c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-04-05 10:56:16 -05:00

38 lines
1.1 KiB
Plaintext

######################################################################
# #
# ** IMPORTANT ** #
# #
# THIS FILE IS ONLY USED BY TOX IN THE CHECK AND GATE JOBS. YOU MUST #
# UPDATE bindep.txt TO INCLUDE ADDITIONAL PACKAGES NEEDED IN THE #
# POST-MERGE # JOBS SUCH AS "tag-releases". #
# #
######################################################################
pbr>=1.6
# NOTE(dhellmann): We pin keyring because new releases tend to add
# dependencies for GUI tools that we don't use
keyring==7.3
requests>=2.5.2
PyYAML>=3.1.0
yamlordereddictloader
prompt_toolkit>=2.0.7
tqdm
mwclient==0.8.1
jsonschema>=2.6.0
twine>=1.13.0
# For release notes generation.
Jinja2>=2.6 # BSD License (3 clause)
parawrap
reno>=2.0.0
sphinx>=1.6.2 # BSD
pyfiglet>=0.7.5
appdirs
packaging>=16.5
openstack-governance>=0.1.0 # Apache 2.0