requirements/blacklist.txt
Jiri Podivin 99881be36e Adding ansible-core to the blacklist
Ansible core is going to take the role of ansible in some projects,
as the dependencies move to the ansible>2.10.

Right now that's the case only for VF, but more might come in
the future and it's best to be ready.

The inclusion of the ansible-core on the blacklist would serve
exactly the same purpose as the inclusion of original ansible package.

Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I36331013568a36c963c180db10e30c3b72cf86a8
2021-09-06 14:06:44 +02:00

54 lines
1.3 KiB
Plaintext

# linters - each project may have a different version with loose convergence
# over time.
astroid
ansible-lint
bandit
flake8
flake8-docstrings
flake8-import-order
flake8-logging-format
hacking
isort
mccabe
pep257
pep8
pre-commit
pyflakes
pycodestyle
pylint
yamllint
# The following Neutron libraries need to be blacklisted
# as they do not use cycle-with-intermediary. The only time they
# would be updated is at release time.
networking-bagpipe
networking-bgpvpn
networking-l2gw
networking-odl
networking-sfc
neutron
neutron-dynamic-routing
neutron-fwaas
neutron-lbaas
neutron-vpnaas
vmware-nsxlib
# Sahara uses cycle-with-rc, but it promises a stable plugin interface
sahara
# Projects are free to specify their own version of ansible
ansible
ansible-core
# Tempest and its plugins are branchless which means master version of these
# tools are used in testing the master + stable branches (except EM stable branch
# where we pin the Tempest and plugins for testing). Keeping Tempest in the
# u-c file will block testing the master + stable branches with Tempest master.
# Bug#1916771 for more details.
# Once any stable branch move to 'Extended Maintenance' and we pin the
# older Tempest to test them then we can move it from here to u-c file.
tempest
# annoying from setuptools
pkg_resources