Addition of custom code style checks into pep8 gate

Registered by Anastasia Kuznetsova on 2015-12-10

During code review it is an usual situation when reviews ask to add / remove extra blank line, rename variables, fix indentation and so on.
To make review process better it would be great to have project-specific list of code style rules, which will be documented and added to our pep8 gate that will catch them too.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Anastasia Kuznetsova
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

https://etherpad.openstack.org/p/mistral-additional-codestyle-checks

<d0ugal> Do we really need this blueprint? It is over 6 months old and there are only two very subjective proposals in the etherpad. I don't think either really help with the readability, and I even if you do think they help a bit, I can't see how you would justify the extra work to enforce them. It strikes me that it would be much better to stay consistent with the standards across OpenStack and the larger Python ecosystem. I am -1 to this proposal as it stands.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.