Many deprecations are triggered early (on imports, for example).
To make sure all DeprecationWarning messages are emitted we enable
them via the PYTHONWARNINGS environment variable.
Change-Id: Ib61fa1f8dfdf0aa4c0e23d7472058244d6b66c53
Now that there exists only a gate job for Python 3.5 and not 3.4,
we should remove those references to the 3.4 that is untested.
Change-Id: I03caf829a7b1a07345bb29f07629c575fdab22a9
Jenkins was failing when coverage report was getting gererated
as coverage combine deletes the reports and essentially and thus
was failing with the message no data found. This patch fixes it
Change-Id: I83ba65eff80181f06e712ea0a75e97919edf50ae
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: If31d87617e59c1fd59da183ac56148d32ef54b6d
Bandit is considered a linter much like pep8. So by request from
the infra team, the bandit job is being made part of pep8 venv.
The bandit testenv needs to stay however for the bandit integration
job.
Change-Id: I83d27217a9ffe8a882342442072272a250eb818c
Latest g-r version of bandit does not require a bandit.yaml any
longer. This removes the bandit.yaml and the anchor gate profile
(which was not part of a gate job).
Change-Id: I1f6f9b8590f44e15662ea2f4212fbd68c072e422
Anchor currently fixes the version of bandit to use as 0.10.0.
And because it was in a separate test-bandit-requirements.txt file,
the OpenStack proposal bot never updated it.
This change removes the separate file and merges into regular test
requirements. As a result, bandit version will jump to 0.17.3
Change-Id: I0988f603d20a2bd21928d1bf009e32db901168a2
Additionally remove coverage files before the run, because they're not
compatible with standard coverage results and could cause failures.
Change-Id: I5937ed1b04bda0741b41972808107829f589ec9e
Coverage files should be erased after every run. Otherwise different
versions of python may try to generate conflicting versions of the
.coverage file and fail to report.
Coverage can still be run separately using tox's coverage target. It
will leave the files behind.
Change-Id: I7d1a4e9bb8195f331d8078fd45d65deae2175ff9
This should allow our documentation to post to
http://docs.openstack.org/developer/anchor
Running locally both pass:
python setup.py build_sphinx
tox -e venv python setup.py build_sphinx
"tox -e docs" still works and you can run
that if you desire.
"tox -e venv python setup.py build_sphinx"
is what's required to work by infra so that
documentation can be built upstream and
published to the developer documentation pages.
It also allows the documentation jobs to run in
the gate so that documentation is built at
review time.
Change-Id: If67961a1b68223ed4ca002037cb7e8c6a51fbe3e
`tox -e docs` will both generate and validate the documentation. The
documentation itself needs to be completed over time.
Change-Id: I2eb790a014f9b4838cfa64054a7d99d9bd339c6a
Remove the specification in tox.ini that _ is a builtin so that
it will no longer assume that _ does not need to be imported.
This helps ensure that the _ from i18n is used.
Activating this check did not flag any violations.
Change-Id: I8a263df35307324804f8d679f9b72339d82df2b7
Remove final issues and enable py34 environment in tox.
Two lines need #noqa tags due to `file` losing the built-in status
in python3.
Change-Id: Id8482647e28e1cb8cbf99ccb2208d78a32dc439c
Initial bits n bobs to get a working Bandit test env for tox, we
can tweek this going forward to tune our test Bandit tests etc
This is not run as part of the normal tox command, run it with
tox -e bandit
Change-Id: I257b0ac335929ad09c43f5753feaab10c269d232
There are a lot of changes needed to support py33, so it would
be a lot easier to just discontinue support for the time being.
I reorded the tests to avoid an incompatibility when pypy and
py27 in the .testrepository directory. If pypy is run first,
the tests run successfully.
Change-Id: Ia03fb203974c7956f00c768a52ba9443c004a6c3
lhinds