Update minversion of tox to 3.9.0 to allow inline comments.
Add skipsdist and ignore_basepython_conflict for better compatibility
and to use correct python version when specified.
Move pep8 test requirements to tox.ini for easier management and update
requirement versions.
Fix a small typo found with new pep8 deps.
Add py27 constraints file for Python 2.7 tox jobs.
Use wallaby jobs.
Remove lower-constraints (it was not used anyway).
Fix docs job
Change-Id: I1132814a86b46a154b3a8eed5bc3e73ad7950589
Set flake8-import-order version to 0.17.1
Full py3 compatible version.
Add all Python3 modules to stdlib list.
Change-Id: I3ef01e49c0e6822368146434f056ac7a1aa7ce4d
The new version enables a lot of standard flake8 checks, so a few
fixes are required. W503 is disabled as it conflicts with W504
and the latter seems to be preferred nowadays.
Change-Id: I0d2fa8c88f081d553ebefb5f764397b2761dc2b5
Replace obsolete sphinx-build job with tox-docs job, use
a template for this.
The newer job uses "tox -e docs" directly.
Add sphinx requirements for python 3.
Change-Id: I1acc55a470ebacce812ba6840663302d759f69b7
For keepalive, there are applications that can self heal and
would rather close an idle session instead of keeping it alive.
If the caller knows exactly that it wants to be administrator,
then do not automatically allow the session to downgrade to
operator.
Change-Id: Iefaf04387e28da9d7f2c613d567cd83ce69c2c03
hacking is not capped in g-r and it is in
blacklist for requirement as hacking new version
can break the gate jobs.
Hacking can break gate jobs because of various
reasons:
- There might be new rule addition in hacking
- Some rules becomes default from non-default
- Updates in pycodestyle etc
That was the main reason it was not added in g-r
auto sync also. Most of the project maintained the
compatible and cap the hacking version in
test-requirements.txt and update to new version when
project is ready. Bumping new version might need code
fix also on project side depends on what new in that
version.
If project does not have cap the hacking version then,
there is possibility of gate failure whenever new hacking
version is released by QA team.
Example of such failure in recent release of hacking 1.1.0
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html
Change-Id: I5f17ec6f67c7e7addfc5b2b2a3f17719402d9c0b
According to OpenStack summit session [1], stestr is
maintained project to which all OpenStack projects should
migrate.
Let's switch to stestr as other projects have already
moved to it.
Uses environment inclusions which need tox 2.8.1 due to
a bug fix. So increase the tox minversion.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: If6eded0dd802cbdfe49ad72c64004585d4a1484b
Create a tox environment for running the unit tests
against the lower bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the
lower bounds in those tests.
Add openstack-tox-lower-constraints job to the zuul
configuration.
See [1] for details.
1. http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
Change-Id: I0f8b1bd44cd2f401593ce079cdecce5020807051
Trying to remove usage of d2to1 - it can cause breakages.
Also, had to fix hacking 102. Turns out it expects copyright headers in
comments, not docstrings.
Change-Id: I3494349ffe2d4cba9c8bcb73408d60bbc12eff5e
Rearranged Sphinx.
Put project under PBR control.
Added tox file.
Added .testr.conf file in anticipation of testr testing.
Change-Id: I55180a6a3d224816c82999bf66156c7874786b17
