Go to file
Joe Gordon ec1f00a07c Add note about checks have community support
This project is only trying to enforce the agreed upon style guide, not
dictate it.  We do not want a new check added if there is any doubt the
check from the community.  Because this project has very a limited
number of reviewers we have to be extra careful about dictating style to the
rest of the community. Consensus in hacking reviewers is not community
consensus.

Change-Id: Id7aaefb8fb98b365f45c8eeb3aa53de02b9cb4e6
2013-06-24 15:02:12 -07:00
2013-03-18 12:19:25 -07:00
2013-03-18 12:19:25 -07:00
2013-03-18 12:19:25 -07:00
2013-05-24 19:58:36 +00:00
2013-05-31 16:11:22 -07:00
2013-03-18 12:19:25 -07:00
2013-03-18 12:19:25 -07:00
2013-06-20 10:18:00 +01:00
2013-03-19 17:12:30 -07:00
2013-06-07 15:43:25 -07:00

Introduction

hacking is a set of flake8 plugins that test and enforce the OpenStack Style Commandments, HACKING.rst.

Versioning

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.

Adding additional checks

Each check is a pep8 plugin so read

https://github.com/jcrocholl/pep8/blob/master/docs/developer.rst#contribute

Requirements

  • The check must already have community support. We do not want to dictate style, only enforce it.
  • The canonical source of the OpenStack Style Commandments is HACKING.rst, and hacking just enforces them; so when adding a new check, it must be in HACKING.rst
  • False negatives are ok, but false positives are not
  • Cannot be project specific, project specific checks should be Local Checks
  • Docstring tests
  • Registered as entry_points in setup.cfg
  • Error code must be in the relevant Hxxx group

Local Checks

hacking supports having local changes in a source tree. They can be configured to run in two different ways. They can be registered individually, or with a factory function.

For individual registration, put a comma separated list of pep8 compatible check functions into the hacking section of tox.ini. Like

[hacking] local-check = nova.tests.hacking.bad_code_is_terrible

Alternately, you can specify the location of a callable that will be called at registration time and will be passed the registration function. The callable should expect to call the passed in function on everything if wants to register. Such as:

[hacking] local-check-factory = nova.tests.hacking.factory

Description
RETIRED, further work has moved to Debian project infrastructure
Readme 937 KiB