[openstack-dev] [all] Why do we have project specific hacking rules?

Ihar Hrachyshka ihrachys at redhat.com
Mon Oct 3 07:01:01 UTC 2016


Andrew Laski <andrew at lascii.com> wrote:
>
> A further hindrance to moving these checks to be OpenStack wide is that
> each check violation is a failure. So in order to roll a new check out
> across projects it requires a lot of churn in each project which
> violates the checks. I would prefer to leave it up to each project to
> make the decision to incorporate a new check and take the review load.
> Ultimately what I think sounds good would be a central listing of checks
> that are in use across projects and then leave it up to each project to
> replicate those that they like.

Late flake8 releases support off_by_default decorator that allows to add  
checks that are not triggered unless explicitly enabled in tox.ini with  
select= directive. That should allow to maintain code in single place while  
still having projects to opt-in new checks.

Ihar



More information about the OpenStack-dev mailing list