Bug 1199423 - Use flake8 and hacking instead of pep8 for Python syntax checks
Summary: Use flake8 and hacking instead of pep8 for Python syntax checks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: z2
: 6.0 (Juno)
Assignee: Martin Magr
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 08:59 UTC by Lukas Bezdicka
Modified: 2023-02-22 23:02 UTC (History)
4 users (show)

Fixed In Version: openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-07 15:10:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 148842 0 None None None Never
OpenStack gerrit 148886 0 None None None Never
OpenStack gerrit 148887 0 None None None Never
OpenStack gerrit 148888 0 None None None Never
OpenStack gerrit 148924 0 None None None Never
OpenStack gerrit 156915 0 None None None Never
OpenStack gerrit 156918 0 None None None Never
OpenStack gerrit 157286 0 None None None Never
Red Hat Product Errata RHSA-2015:0789 0 normal SHIPPED_LIVE Important: openstack-packstack and openstack-puppet-modules security and bug fix update 2015-04-07 19:08:02 UTC

Description Lukas Bezdicka 2015-03-06 08:59:54 UTC 
Openstack upstream is using fake8, we should switch from pep8 to it and enable appropriate checks.
Comment 3 Lukas Bezdicka 2015-03-06 09:08:39 UTC 
Packstack should now use fake8 for code formatting and syntax checks.
Comment 5 Ami Jeain 2015-03-15 09:05:49 UTC 
an internal code change. Only packstack regression test is required
Comment 6 Ido Ovadia 2015-03-15 22:16:27 UTC 
Verified
========
openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost.noarch
Comment 8 errata-xmlrpc 2015-04-07 15:10:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0789.html
Note You need to log in before you can comment on or make changes to this bug.