The mock third party library was needed for mock support in py2 runtimes. Since we now only support py36 and later, we don't need it in lower-constraints and requirements. These changes will help us to drop `mock` from openstack/requirements Change-Id: I71a09f2eddd3a344225cb69f9679e99fdeb3e2db
|1 month ago|
|doc||1 month ago|
|hacking||3 months ago|
|integration-test||1 year ago|
|releasenotes||1 month ago|
|.gitignore||2 years ago|
|.gitreview||1 year ago|
|.mailmap||7 years ago|
|.stestr.conf||2 years ago|
|.zuul.yaml||1 month ago|
|CONTRIBUTING.rst||2 months ago|
|HACKING.rst||1 year ago|
|LICENSE||7 years ago|
|MANIFEST.in||6 years ago|
|README.rst||3 months ago|
|lower-constraints.txt||1 month ago|
|py35-upper-constraints.txt||1 month ago|
|requirements.txt||2 months ago|
|setup.cfg||2 months ago|
|setup.py||3 months ago|
|test-requirements.txt||1 month ago|
|tox.ini||1 month ago|
hacking is a set of flake8 plugins that test and enforce the OpenStack StyleGuide
Hacking pins its dependencies, as a new release of some dependency can break hacking based gating jobs. This is because new versions of dependencies can introduce new rules, or make existing rules stricter.
hacking is available from pypi, so just run:
pip install hacking
This will install specific versions of
flake8 with the
Hacking started its life out as a text file in Nova's first commit. It was initially based on the Google Python Style Guide, and over time more OpenStack specific rules were added. Hacking serves several purposes:
Initially the hacking style guide was enforced manually by reviewers, but this was a big waste of time so hacking, the tool, was born to automate the process and remove the extra burden from human reviewers.
hacking uses the
major.minor.maintenance release notation, where maintenance releases cannot contain new checks. This way projects can gate on hacking by pinning on the
major.minor number while accepting maintenance updates without being concerned that a new version will break the gate with a new check.
For example a project can depend on
hacking>=0.10.0,<0.11.0, and can know that
0.10.1 will not fail in places where
Each check is a pep8 plugin so read
The focus of new or changed rules should be to do one of the following
But, as always, remember that these are Guidelines. Treat them as such. There are always times for exceptions. All new rules should support noqa.
If a check needs to be staged in, or it does not apply to every project or its branch, it can be added as off by default.
Some of the available checks are disabled by default. These checks are:
To enable these checks, edit the
flake8 section of the
tox.ini file. For example to enable H106 and H203:
hacking supports having local changes in a source tree. They need to be registered individually in tox.ini:
Add to tox.ini a new section flake8:local-plugins and list each plugin with its entry-point. Additionally, you can add the path to the files containing the plugins so that the repository does not need to be installed with the paths directive.
The plugins, in the example above they live in nova/hacking/checks.py, need to annotate all functions with @core.flake8ext
Further details are part of the flake8 documentation.