releases/requirements.txt
Doug Hellmann 9b8f290117 use packaging to determine the canonical name for projects on PyPI
Rather than applying the rules ourselves, use the packaging project
utility function to prepare the canonical name.

Change-Id: I6310585ff14c376e954b0edc9def67cd65a5d550
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-03-07 10:49:50 -05:00

36 lines
1.0 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
tqdm
packaging>=15.2
mwclient==0.8.1
jsonschema>=2.6.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