Run pep8 checks against output of update.py

Registered by Doug Hellmann on 2014-01-22

https://bugs.launchpad.net/oslo/+bug/1271625 can't be the first time we have had an issue with pep8 line lengths because of the substitution of "oslo" by update.py. We should automate a check by running update against a tmp dir with a fake project using a long name and then re-running flake8 over the results.

Blueprint information

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

Related branches

Sprints

Whiteboard

@Doug,
Is this still valid ? Can we check the line with 'oslo' which can be found with same rule in update.py, then calculate len(line) + len(longest_porject_name) - len('oslo') > 79 to judge if the oslo-incubator is good ? I think this can be added in local hacking in
https://blueprints.launchpad.net/oslo/+spec/oslo-local-hacking -gcb

Gerrit topic: https://review.openstack.org/#q,topic:bp/pep8-on-update,n,z

Addressed by: https://review.openstack.org/93036
    hacking: Don't exceed 80 characters after replacing oslo with base name.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.