networking-midonet

flake8-import-order usage is not ideal

Bug #1703554 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-midonet
Fix Released
Undecided
Unassigned

Bug Description

flake8-import-order usage is not ideal.
at least we should configure application-import-names properly.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-midonet (master)

Reviewed: https://review.openstack.org/482450
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=8dccb738dbf743acb769fb33860cb3d69e95d190
Submitter: Jenkins
Branch: master

commit 8dccb738dbf743acb769fb33860cb3d69e95d190
Author: YAMAMOTO Takashi <email address hidden>
Date: Tue Jul 11 17:41:42 2017 +0900

    pep8: Configure flake8-import-order properly

    Closes-Bug: #1703554
    Change-Id: Id77c5fafaf4ccf168903914975004915507886ea

Changed in networking-midonet:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-midonet 5.0.0.0b3

This issue was fixed in the openstack/networking-midonet 5.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.