'pip install -U' ugrades specified packages, this is not necessary
since we use constraints, remove the parameter '-U' from the line.
With tools/tox_install.sh - which a previous change of mine removed -
the -U was not harmful, but with the current set up, it might cause
upgrades, so remove it.
Change-Id: Idf400c13258ecbe0e986a31fd747ab9ba42d25ed
We do not need tox_install.sh, pip can handle constraints itself
and install the project correctly. Thus update tox.ini and remove
the now obsolete tools/tox_install.sh file.
This follows https://review.openstack.org/#/c/508061 to remove
tools/tox_install.sh.
Change-Id: Iabc08e643c5978b486d966b824b70ac92b45b4cc
Add the bandit security scanner to the pep8 job.
Change-Id: I4fa14f3c42f064b6ec58e1f3a3cde22ad031ac7a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The documentation jobs now look for requirements in
doc/requirements.txt and do not use tox for release notes. Move the
dependency list from setup.cfg to the new file and update tox.ini so
the developer experience is consistent with what the CI system does.
Change-Id: I739c9eba21d1b9a680d6b0e9cc6a4cbaca56e543
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
.
Change-Id: I84ff1e6675f272d68055037634833836bc26a9fd
reno is not used for testing so it should not be in test-requirements.txt .
Move it to the optional docs requirements.
Change-Id: Idf09d2fe9632882a830311a1ab1fe28b72f1d5d9
Looks like the requirements bot can not handle comments correctly. Commit
95f3944a60ff removed the correct indent and commit 6b31e1de17ae added
a duplicate openstackdocstheme requirement instead of updating the
available one.
Solving this for now with the removal of the comment itself.
Change-Id: I6e25e8d626254b112b3ba5e525d89791ea4a25f2
stevedore is a library that is used outside of OpenStack, too. Having
a build requirement that needs something OpenStack specific makes
life in cases (eg. for downstream packagers) more difficult.
So let's make openstackdocstheme an optional requirement.
Change-Id: Ic8cc577e617e5da699f9dc43830183005bd2ee66
The ExtensionManager.items() method is analogous to the Mapping.items()
method.
(This also refactors the _extensions_by_name generation logic out of
__getitem__.)
Change-Id: Iad3a58aec7908eb3a829892bbea567705ab2dd97
It is not needed and stevedore is a fundamental package which should
try to keep its requirements list small.
Change-Id: I701613977f6c243c13d118d8822fe5db0e12f97e
The gating on python 3.4 is restricted to <= Mitaka. This is due
to the change from Ubuntu Trusty to Xenial, where only python3.5
is available. There is no need to continue to keep these settings.
Change-Id: I8899429c4bdbc723c448624be49cc27343798f25
This allows to get the list of valid entry points names declared for a
namespace, without loading them.
Change-Id: If9132edc14c2772732fd4ec0dc5dc3ebc4a56b3c
